72
Libadwaita: Splitting GTK and Design Language
(tesk.page)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jun 2024
72 points (93.9% liked)
Linux
48214 readers
717 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
That was a good read. I’d not really been sure of the differences between libadawaita and GTK were. It sounds like this frees up GTK to focus on being a cross platform GUI library, perhaps competing more directly with Qt. Meanwhile, libadawaita allows GNOME developers to keep leveraging GTK and tune it to their design guidelines.
I’ve only seen positive things come out of recent GNOME apps, but I wonder if the downside of GTK no longer embedding GNOME’s design language would be apps choosing to use GTK directly instead of libadawaita for better cross platform support. Will we end up with a less cohesive GNOME environment in the future?