• 5 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle





  • Wtf. It’s obviously crashed because of how absolutely unusable and disgusting youtube has become. I used to use youtube for 3 4 hours a day, but in the last year it may have gotten to an average of 20mins. Because you have to sign in to your google account to watch a video, many of videos cant be viewed with a vpn (which is how very large population of the world use youtube) and the overall quality of content has dropped massively, specially with 3/10 videos and shorts being AI slops.




  • 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.


  • 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.





  • Yes. Wayland just isn’t as mture as X11 you have to fiddle with everything to work. Each wm/de (they’re called compositors now? Wtf?) Now has it’s own plethora of config, whilst on xorg you just configure your wm, you configure your compositor, everything is standalone and modular.

    A main issue with wayland for me is absolute atrocious performance when connected to external display (nvidia gpu). Another is no simple redshift alternative. Everything is just hard in wayland. And some of it isn’t just because of it’s less maturity (it’s been around for decades), it’s because it is hard by design and puts way too much responsibility and load on small wm,de maintainers.


  • I use both niri and i3wm.

    Here is my take: i3wm is amazing. It’s my preferred wm for keyboard and mouse workflow and professional work. Everything just works, your mind is clear, you have tabs which is literally the same concept as niri but cleaner. And you can structure your workspace very efficiently.

    Niri is also great, my main problem is with wayland itself. I don’t care what anyone says, all my things work much more simple and with less effort under X11 and the fragmentation of wayland ecosystem drives me nuts. I’m not a fan of hacking your way into every single thing you want to do and exploring a plethora of docs for everything. But lets forget about this.

    Niri itself is amazing for a laptop touchpad workflow. It is so efficient, enjoyable and cool when you have a touchpad. But it’s not as organized and efficient for serious work with many windows as i3wm. But for light work it’s just delightful.



  • Love to see the TS and python “experts” in the comments having no idea what’s going on.

    Clojure is awesome and is meant to be used like this. Clojure is a Hosted language specification, meant to be implemented on different runtimes. That’s why we have clojurescript, jvm clojure, babashka and jank.

    Jank seems like an amazing and exciting idea to have clojure with higher performance and smaller footprint of cpp, and also it’s ecosystem.