Instead of spending the substantial donations they received[1] on who knows what, the GNOME foundation should have spent some of it conducting proper focus groups.
1: https://www.gnome.org/news/2018/05/anonymous-donor-pledges-1...
I think it's an interesting and worthwhile experimental path; I just wish it wasn't the "default" as much as it is. But I also feel that way about Ubuntu. And Windows. xD
One of my least favourite was when it was not possible to configure the screensaver timeout to never turn off the display. IIRC you had a choice of several fixed times, from 5 minutes to 4 hours, but no "Never" option.
Not useful for systems which display information and are infrequently interacted with. That use case was completely ignored, and for no good reason.
oh no doubt, I have another comment from 4+ years ago about the same topic https://news.ycombinator.com/item?id=10883631 and even then it was ancient history IIRC
man, just looking at that page again reminded me that Windows Registry for Linux^W^W^W^W gconf exists.
>Icon Themes can change icon metaphors, leading to interfaces with icons that don’t express what the developer intended.
Icons were never sufficient metaphors to start with which is why we have text labels.
>Changing an app’s icon denies the developer the possibility to control their brand.
What does this even actually mean.
>User Help and Documentation are similarly useless if UI elements on your system are different from the ones described in the documentation.
This is only true if the user is completing an action that is solely based on clicking an icon with no text which we have already established is bad.
>The problem we’re facing is the expectation that apps can be arbitrarily restyled without manual work, which is and has always been an illusion.
Why has this worked generally fine in lots of ecosystems including gnome?
>If you like to tinker with your own system, that’s fine with us.
Earlier discussion seemed to suggest that lots of gnome developers were in fact not fine with this because it hurt gnomes "brand identity"
>Changing third-party apps without any QA is reckless, and would be unacceptable on any other platform.
Reckless?
> we urge you to find ways to do this without taking away our agency
Your agency?
> Just because our apps use GTK that does not mean we’re ok with them being changed from under us.
Nobody cares if you are OK with it.
Because it’s now possible to run multiple VMs at once (containers, etc) perhaps it’s time to run a simple, minimal, admin friendly hacker vm inside Ubuntu desktop?
Let Ubuntu configure all that it needs to get a good functional machine out of the box (working sleep mode for laptops, WiFi management, GPU support, systemd if that’s what it wants.) I then deploy the minimal VM I actually want to poke around with inside that installation.
This is pretty much what many people do in macOS. Apple’s OS supports the bare metal, vagrant / VirtualBox give me my tractably scrutable dev environment.
It’s not a particularly ground breaking concept but it might cheer me up a bit when battling with the volatility of user facing Linux distributions.
> Let Ubuntu configure all that it needs to get a good functional machine out of the box (working sleep mode for laptops, WiFi management, GPU support, systemd if that’s what it wants.) I then deploy the minimal VM I actually want to poke around with inside that installation.
If there's anyone like me here they might be happy to know that KDE Neon exists and is something like:
- Stable Ubuntu base.
- Infinitely (almost) customizable KDE on top.
- And (IMO unlike Kubuntu) sane defaults.
[0] is the example that always comes to mind. I guess this made sense to somebody at the time, but it adds overhead to a process that was simple before, and isn't enabled just for "Enterprise" deployments, it's just dumped on the user to figure out how to configure screensaver hack settings by creating / modifying a theme.
[0] https://wiki.gnome.org/Attic/GnomeScreensaver/FrequentlyAske...