I used to always bounce back and forth between Gnome, Plasma, Sway and Hyprland.
I love tiling compositors, but I also love having a fully functional desktop without stitching together two dozen different tools and configuring each separately. I got better things to do than edit text files for days.
And I think I found my holy grail: niri with Dank Material Shell.
DMS really is something else. A fully-fledged DE that sits on top of a tiling wayland compositor, with a workflow similar to Gnome and GUI customization options similar to Plasma.
I realize I’m shilling hard here, but I don’t even know the guy who made it. I’m just genuinely floored by the project’s quality.
ZIrconium is a cool Bootc with Niri “distro” https://zirconium.gay/
I hate to be that guy but dev is vibe coding it. Check the .gitignore
I don’t know what that is or how to check it, and frankly I don’t care that much if they’re using AI.
I didn’t notice any bugs so far and I’m not relying on it for mission-critical work.
If I boycotted everything that’s made with AI help, I’d have to go back to Slackware.You probably couldn’t boycott everything made with LLMs even if you went back to slackware. Firefox devs use it too (and for the love of god, no one attack the dev for it).
I don’t like it, consider it a liability, mentioned it to those who might care. I do appreciate your post nonetheless, not my cup of tea as an environment but I still liked the post.
Thank you for bringing this up! But, while you’ve clearly pointed out where to look at, it wasn’t quite enough for me to understand what exact content gave it away. Was it
- short/brief .gitignore?
- /target?
- /result?
- Any combination of the above?
I desire to learn this in the hopes of improving my vibe-code radar.
It wasn’t just the .gitignore to be honest, just a set of “rules” I have on a script I use to analyze repos (I may publish it eventually, although it would quickly become worthless plus it’s used at work to vet dependencies) and then just manual review of commits.
Ah, okay. I was looking at niri’s .gitignore 😅. But yeah, I can see it now. Thanks again!
The heretic rejects the truth of KDE Plasma! Burn them!
With the sarcasm now out of my system, I will definitely give this a try. Thank you for the tip. The tiling feature in COSMIC is amazing, but the rest of the environment is still rough. I would love to see more like that.
Niri is awesome, but I cannot stand DMS with how often it completely changes the base setup and breaks my configs. The generated json dotfiles are also a mess, impossible to work with outside of their GUI. My friend tried it and switched to Noctalia, and he’s much happier. I’m probably just going back to Waybar or something simpler, but that’s just personal preference
I followed the same path as OP and your friend in the last week. I settled with Niri and Noctalia and am very happy.
Off topic but Berm Peak is awesome.
That looks pretty nice! Next time I play around, I’ll have to try that. I’ve got Cinnamon dialed in pretty well at the moment on my main desktop. And I finally got LXQt, Openbox, and Picom to a state I’m happy with on my turd of a laptop. Can you put the panel on the bottom?
Yes, click on the clock, then Settings -> Dankbar -> Settings -> Position -> Bottom
what are you using for a file manager?
yazi
Because it’s easy to configure an “open with…” dialog with multiple options per mime type.
I often want to open image files with gimp, but don’t want it to be my default image viewer.
how is resource consumption? how is the hardware you are running it on?
It uses 1.2GB of RAM compared to 800MB for niri without dms, and idles at 5% CPU load.
I run it on an 8-year-old Thinkpad E480 with an i5-8250U and 16GB RAM.
I’ll have to check this out! I’ve had an itch to use labwc but didn’t look forward to configuring everything.
this is an insanely professional-looking project, the (potential) vibed-ness notwithstanding. sadly, unless there’s some post describing what for and how claude & friends is used, not even thinking of touching that.
Would it work on BSD?
Maybe. Its only hard dependency is quickshell, which seems to be available for FreeBSD: https://github.com/charlesrocket/quickshell/tree/fbsd
It doesn’t depend on systemd.
But I’d be very surprised if it works as intended out of the box without some fiddling.
In any case, you’d have to install it manually. The provided scripts are only for Linux.looks great. I will give it a try. I dream of using freeBSD as a computer