3 ms·
This is (slightly) misconstrued. Dark themes were not exclusively available through Tweaks, all that app did was force the Yaru-Dark stylesheet onto all third-p
by smoldesu 5y ago
This is (slightly) misconstrued. Dark themes were not exclusively available through Tweaks, all that app did was force the Yaru-Dark stylesheet onto all third-party apps. As such, they kinda doctor their history here: GTK has always supported arbitrary themes, including dark ones, but the interface for changing it was not directly exposed in the settings. With the advent of GNOME 42, the team has attempted to replace the versatility of the old method with an officially supported light and dark theme. Also, GTK apps never had to opt-in to adding a dark theme: they all linked against GTK/glib, which meant that any global stylesheet changes would force them to change their appearance.
I frankly don't think this will last, and Ubuntu's "we're still using both ways" feels like a subtle concession that the old way was best. The GNOME maintainers need to take a long, hard look at their downstream users and consider if the constant whiplash and "my way or the highway" attitude is worth it (or even feasible). They're picking fights with people who don't want to fight and are getting tired of being ignored: first it was Elementary, then it was Pop_OS!, and now it looks like Ubuntu still isn't ready to hand them the keys to the kingdom. My two cents says this is a good thing: Linux is modular, and maintaining that modularity is paramount. The changes made with GTK4, GNOME 4x and Libadwaita have really done nothing for users or developers, which kinda makes me wonder why they're continuing to cull features nearly 3 minor releases later. Are we building to anything here?