HNHacker News
TopNewBestAskShowJobs

crashdancer

6 karma · joined June 3, 2024

submissionscomments
crashdancer··on Libadwaita: Splitting GTK and Design Language
>bad decisions from the gnome foundation. They can go under for all I care.

This won't help anything. GNOME Foundation doesn't really have anything to do with the development of GNOME or GTK. The Foundation is just the financial entity that does fundraising and owns the hosting. Actual development is decided by developers, i.e. the volunteers who show up to maintain it.

>Overall I truly believe they did a disservice to the whole Linux Desktop and the community over the last 15 years.

Speak for yourself please, personally I've enjoyed GNOME for the last 15 years. There's no need to make these kind of normative statements.

crashdancer··on Libadwaita: Splitting GTK and Design Language
>why should other desktop environments work on a different 'design language' library?

The responsive widgets are only a small part of libadwaita. Part of the reason those widgets are still there is because they're still being iterated on -- once a widget gets into GTK it has to be maintained for a long time and GTK developers got burned before by adding a lot of random widgets without iterating first. So the bar is understandably a lot higher for adding new GTK widgets than it is for adding widgets into one of these "design language" libraries.

I could see some responsive widgets getting merged into GTK but only if they become stable enough and everybody (not just GNOME) likes the API wants them in GTK.

>reintroducing proper theming support to libadwaita

It does have proper theming support if you're using it as an app developer. If you mean allowing users to add arbitrary themes to arbitrary applications, that isn't going to happen. It can't be done without breaking applications, and arbitrary theming ruins the whole purpose of it anyway which is to enable all GNOME apps to have a consistent UX and theme.

crashdancer··on Libadwaita: Splitting GTK and Design Language
>But Gnome has been burning user and developer trust for more than a decade

People complained in the exact same way when GTK2 and GNOME 2 were released. There really isn't anything different this time around as to how they approach changes and incremental improvements. It's the same minority of loud complainers blaming GNOME for everything when they could just use something else. It's not like there's a lack of forks and alternatives. And hey, a certain percentage of KDE users complain and fork stuff whenever a new version of KDE comes out too. That's just what happens.

As with anything open source, you get what you put in: if you don't contribute anything upstream, and you're not willing to maintain a fork, and you don't want to compromise, and you expect someone else to always "manage" everything to your liking all the time, then you're setting yourself up for disappointment.

crashdancer··on Libadwaita: Splitting GTK and Design Language
>menu bars are going away because GNOME doesn't use them anymore.

Where did you hear this? This is misinformation, menu bars aren't going away. The API is just changed in GTK4: https://docs.gtk.org/gtk4/migrating-3to4.html#gtkmenu-gtkmen...

>GtkDialog as a notable example

GtkDialog was deprecated because other changes made it now trivial for any app to re-implement dialogs with just a few CSS classes, and it's more flexible that way too.

>a Rust-native UI toolkit library that does its own drawing, but can consume GTK3 themes

This is never going to happen unless you re-implement nearly all of GTK3 in Rust with the exact same widget hierarchies and all the quirks of its (outdated) rendering model. Why would you want this anyway? GTK themes aren't particularly special, it's just CSS.

← PreviousPage 2 of 2