Live data from Hacker News

The Future Is Niri

ersei.net

1–10 of 223 posts

Re: The Future Is Niri

#3
Niri is cool, but was the drag issue reported? :/

sway 1.10 is from october, 1.10.1 is a bugfix from late january. Since they're talking about git bisect, I imagine they might be running master (i.e., bleeding edge) instead of stable releases...

Re: The Future Is Niri

#4
A fun read. Everyone has their breaking point…

> Naturally, instead of figuring out what library made a breaking change and spending four hours running git bisect, I decided to throw nearly a decade of muscle-memory and workflow refinements out the window.

Re: The Future Is Niri

#5
I enjoyed this post but I'm going to keep using xmonad (and X) until I can port my configuration to a wayland equivalent (if that is even possible)

Re: The Future Is Niri

#6
> The worst "street-cred" I have is that I've been using tiling window managers for thirty-five percent of my life: five years with Sway and two with i3. As the realization of those numbers (and my age) dawns upon me

The author is ~21 and seems worried they're old ? I had a good giggle about that.. And then it dawned upon me how old I actually am.

Re: The Future Is Niri

#7
This looks really intriguing and I'm looking forward to using it.

I'm still using i3, which is just barely good enough to work.

I miss Notion, which was unfortunately too flakey and unstable to continue using, but that had one property which it looks like Niri preserves -- opening a new window will never cause a resize event. Notion is perhaps even stronger because there is no infinite canvas; opening a new window will never cause a re-layout. It will always open in a tab or a blank space. Similarly, moving windows won't cause re-layout actions; it will just move them between tabs of existing frames.

My i3 configuration tried to preserve this -- it tries to make everything tabbed by default so that moving windows will just move between tabs rather than into new blanks spaces and cause a relayout action, but sometimes, for some reason, it just ... does not, and instead opens a new split.

I tried to make xmonad work but I'm not good enough at Haskell to figure out if it was even possible to configure it the way I want.

Re: The Future Is Niri

#8
I would like to know, coming from a traditional tiling window manager, how does the shortcut workflow look like?

For me the number one thing is having fixed shortcuts á la Super+[0-9] to go to specific windows / workspaces / essentially a specific program. If I can have that, and additionally solving the "worskpace management" problem as TFA described, I'm sold!

Does it make sense to use "workspaces" like this with Niri? For example, one workspace with the browser, one with the editor, one with several terminal columns, and so on. I would need to "switch" (immediately, without animation effects, please) e.g. from "browser" to "terminals".

Re: The Future Is Niri

#9

I would like to know, coming from a traditional tiling window manager, how does the shortcut workflow look like? For me the number one thing is having fixed shortcuts á la Super+[0-9] to go to specific windows / workspaces / essentially a specific program. If I can have that, and additionally solving the "worskpace management" problem as TFA described, I'm sold! Does it make sense to use "workspaces" like this with N…

Yes, Niri still supports numbered workspaces in the same was as WMs like Sway. It's just that now you can scroll them horizontally too.

Re: The Future Is Niri

#10
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.

Post reply on HN