These days, I daily drive Niri and love it. I love the workflow of a scrolling WM. I love that I can configure it via a single text file in the standard configuration directory, I love how lightweight it is. It’s just about perfect for me.
These days, I daily drive Niri and love it. I love the workflow of a scrolling WM. I love that I can configure it via a single text file in the standard configuration directory, I love how lightweight it is. It’s just about perfect for me.
But enough about Mac OS Tahoe!
Apple should at once hire the people who are responsible for Gnome's UI, because they've got it figured out. Even better, put back together the Nokia N9 GUI team.
macOS is nearly the opposite in this regard. I wouldn’t mind giving it a facelift but doing it GNOME style would mean it losing much of what has kept many users on it.
Often it functions as a “do this for everything” modifier. So for example, option-clicking the minimize traffic light minimizes all windows from the application the window belongs to, and option-clicking a disclosure triangle in a nested list expands or contracts all child nodes.
There’s tons of little things like that which might sound silly but become significant time and sanity savers after making a habit of using them.
I'm a regular Linux user, but I wouldn't know how to get all the data from the Wi-Fi applet using the Command Line. GUI have the advantage of discoverability over CLI: with a GUI I get a bunch of useful info in a single place, with a CLI I first need to know that a data is available and then I need to look-up the right invocation to get this data.
Well, for a start, `ip` isn't enough to give you anything. You'd need at least `ip a` or `ip r`, but then you'd have to already know that or go hunting in the manual (the `ip` help really is pretty bad). For something you might only need once a year (and will forget before you need it again!), having it in the GUI is very valuable.