Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Unfortunately tiling window managers for Linux have become quite stagnant in terms of improving and iterating on workflows, which is probably why we're seeing more of the kind of sentiment expressed in this post lately (of course, the poor backwards compatibility story is not helping either)

The Windows scene is definitely the place where the most interesting workflow advances in "traditional" tiling window managers are happening right now.



Can you point to any innovative Windows tiling WMs and explain what "workflow advances" it makes? All I found was FancyWM, and it seems basically identical to i3.


I'm on a phone for most of today so I won't be making the kind of lengthy reply you're asking for, but you can check out komorebi and jwno if you're genuinely interested


I don't see any real innovation with those WM. It looks like they are just migrating the features of advanced Linux-WMs to the windows-world, in their own way.

Can you name any specific features you are considering as innovative?


The main ones that I'm still waiting to see integrated into mainstream Linux twms are workspace scrolling (of course), dynamic layout rules and dynamic offset rules (important for ultrawide monitor users).

I'd also like to see container limit rules to enforce stacking after meeting a threshold (functions as a hard cap on tiles-per-workspace), and native support for Vimium-style shortcuts for every UI element on the screen (from jwno), but I could probably live without these.

I wouldn't call these particularly innovative features, in fact they are pretty low hanging fruit.


> dynamic layout rules and dynamic offset rules (important for ultrawide monitor users).

What is dynamic offset? And what are you missing from the existing layouts the existing dynamic WMs already deliver?

> and native support for Vimium-style shortcuts for every UI element on the screen (from jwno), but I could probably live without these.

Isn't this impossible with Linux, as the WM has no control over the application on that level? Maybe through accessibility-settings you can gain them on a per app-basis. But this seems more a problem of Desktop Environments than Window Managers.


Since we're >5 layers deep in the thread tree, feel free to hit me up off-platform if you'd like to discuss this more. Again, I'm on my phone today and limited in how much detail I can respond in - but if you are interested enough to dig into the documentation and video resources available you'll find the answers to all of these questions and more.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: