Recent versions of KDE have pretty good tiling support, so it's possible to have a rich DE and good tiling.
Moving Back to a Tiling WM – XMonad
11–20 of 84 posts
Re: Moving Back to a Tiling WM – XMonad
#12Type-checking keybindings is cute, but you're going to discover that the keybinding doesn't work when you go to use it, so how much time are you really saving? That's not helped by the fact that many WMs/compositors have validators for their configs, so you're getting much of the same benefit with much less trouble.
For reference, Niri's config is very approachable: https://github.com/YaLTeR/niri/blob/main/resources/default-c...
Re: Moving Back to a Tiling WM – XMonad
#13Re: Moving Back to a Tiling WM – XMonad
#14Tiling WMs are dead. Long live tiling WMs. Scrolling WMs like Niri/Paperwm are where it’s at now.
Looking at a video demo of Niri for an example: https://github.com/YaLTeR/niri Conceptually, it's like an infinite 2D canvas windows, divided into strips (strip is a workspace), and you then scroll through an infinite ribbon of windows in each strip. Seems interesting, but also slower and less flexible than traditional tiling WMs (least of all because of the slow scrolling animations, but also because it seems to pre…
You can get similar functionality with tabbed windows, but I'm still trying to decide which workflow I prefer; scrolling feels a bit more "organic", while tabs are superior for density.
Re: Moving Back to a Tiling WM – XMonad
#15Tiling WMs are dead. Long live tiling WMs. Scrolling WMs like Niri/Paperwm are where it’s at now.
Looking at a video demo of Niri for an example: https://github.com/YaLTeR/niri Conceptually, it's like an infinite 2D canvas windows, divided into strips (strip is a workspace), and you then scroll through an infinite ribbon of windows in each strip. Seems interesting, but also slower and less flexible than traditional tiling WMs (least of all because of the slow scrolling animations, but also because it seems to pre…
This is opposed to a traditional tiling WM where you'd either need to open the app in another workspace, use some stacking feature or worst of all shove the new window into the current view by resizing some other window(s) which is often not ideal.
Re: Moving Back to a Tiling WM – XMonad
#16I've been on HyprLand for a week now and haven't hit any blockers yet that'd force me to go back to KDE.
Re: Moving Back to a Tiling WM – XMonad
#17I think Claude Code makes TilingWMs doable. I've always given up in the past because there have been reams of configs necessary to get to a fairly usable state, and I don't love reading manuals for desktop environments - but now it's all pretty easy to crank out. I've been on HyprLand for a week now and haven't hit any blockers yet that'd force me to go back to KDE.
Re: Moving Back to a Tiling WM – XMonad
#18Re: Moving Back to a Tiling WM – XMonad
#19Recent versions of KDE have pretty good tiling support, so it's possible to have a rich DE and good tiling.
when you say tiling support, do you mean automatic tiling, or sending it to a corner via key combo?
Re: Moving Back to a Tiling WM – XMonad
#20Configuring your WM in Haskell seems fun, but I suspect "fun" is the primary motivator, not any kind of practical reason. Type-checking keybindings is cute, but you're going to discover that the keybinding doesn't work when you go to use it, so how much time are you really saving? That's not helped by the fact that many WMs/compositors have validators for their configs, so you're getting much of the same benefit with…
Not for me. I don't know Haskell, and I had to cargo-cult forms to do what I want (which bothers me, as someone towards the end of the developer spectrum that likes to understand well how systems work).
But XMonad with a few cargo-culted tweaks works noticeably better for me than I've been able to configure i3wm. I forced myself to use i3wm at one company, for two years, rather than bring over my Xmonad config, and every evening it was a relief to be back using Xmonad on my personal laptop.