97
Niri a scrollable-tiling Wayland compositor (github.com)
submitted 11 months ago by to c/linux@programming.dev
19 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 11 months ago (3 children)

I've used it for a while. It's awesome for basic stuff (checking emails, browsing, etc.), but for professional usage, it gets in the way. You can do the exact same thing with sway/i3 using tabbed windows but with much more control ans customizability, and it's a lot more efficient.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 6 points 11 months ago (1 child)

    I'd be curious what you mean by more control/customizability for sway/i3. I'm using niri now, and came from sway, and haven't really notice a difference in capabilities (although niri has easier animations and the overview). And now I'm wondering if I just wasn't using/understanding sway to the max.

    I think on my multi-monitor setup, sway is maybe slightly better suited, but on my laptop I'm definitely preferring niri--but open to finding out new things about other wms that I missed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 11 months ago (1 child)

    From the top of my head, when working on something in sway/i3 I have my browsers assigned to workspace3, my terminals to ws1, my ide to ws2 and so on. So when I open them they automatically open in those ws, and I always know where to find them. I might have ~20 windows opened across 7-9 different workspaces. I go to ws2, edit my code, see the results in ws3 in my browser, do something in the term, and repeat. I might do this in a loop a lot. The benefit of i3 is that I know exactly where to find what and it's very simple to switch to it. But niri doesn't have fixed workspaces and for finding windows you have to visually search for them. So the process becomes pretty cumbersome.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 11 months ago (1 child)

    Niri does have named workspaces so you can absolutely switch to fixed workspaces like you describe.

    I have fixed workspaces but then temporarily add extra workspaces for side tasks - these are relative to the named ones but don't stop you jumping to your named workspaces (assuming you've got your shortcut keys set up to match).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 11 months ago* (1 child)

    Oh that's cool. This fixes my problem with switching to windows.

    Another issue with niri is you kinda get lost in the infinite scroll. Sometimes you dont know if there are any other windows, or hundred other windows in a workspace. As opposed to sway tabs, that show you exactly how many windows tgere are, what they are, and where you are in your ws.

    Something that would definitely make me fully switch to niri is if you could increntally scroll windows instead of one window at a time. Think I can create a terminal 3 times wider than my monitor, open nvim and create ~10 splits in it and simple switch between them. Bu you just can't do that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •