3 ms·

> I have no intention of installing Libadwaita onto any of my systems Out of curiosity why is this?

• smoldesu 5y ago
  GNOME middleware has no place on my system. GTK4 breaks font rendering which is already eye-searing enough, but libadwaita is woefully incomplete and barely functions without sandboxed life-support propping it up. It also violates the native LAF of my system, introduces compositing issues on any system that isn't running a GNOME 40/Wayland combo, consumes too many resources and frankly has no reason to exist given the modern state of GTK programming. Since I'm a GTK dev, I choose to abstain by staying on GTK3, which has none of the aforementioned issues.
  • kk6mrp 5y ago
    Ok, interesting. I am running Sway on Wayland and have one application that depends on libadwaita. Looking it over, I can see what you're talking about. Thank you for sharing!
  • int_19h 5y ago
    I see that Gnome maintainers are as good as ever at engaging with their community: "You can reopen it. But it is not a bug. ... And it is not a regression either." https://gitlab.gnome.org/GNOME/gtk/-/issues/3787 https://gitlab.gnome.org/GNOME/gtk/-/issues/3787
    • smoldesu 5y ago
      It's pretty terrible. I've feuded with more GNOME maintainers than one person should ever have to, and it always comes down to the same "well we're right and you're wrong" mentality that makes nobody happy. With blurry text in particular, a surprisingly large number of GNOME team members decided it wasn't an issue since the effect could be halfway mitigated with sandboxing, so none of them ever addressed it. I can't use GTK4 or libadwaita confidently, as a developer. It's tooling that was designed from the ground-up to limit my capacity as a developer, and as such I refuse to write code with it or install it on my system, for that matter.