Gtk 4.0 sucks

…and that’s OK.

Meanwhile, Gtk 4.0 will not be the final stable API of what we would call “Gtk 4”. Each 6 months, the new release (Gtk 4.2, Gtk 4.4, Gtk 4.6) will break API and ABI vs. the release that came before it. These incompatible minor versions will not be fully parallel installable; they will use the same pkg-config name and the same header file directory.

https://blogs.gnome.org/desrt/2016/06/13/gtk-4-0-is-not-gtk-4/

React Native > Gtk

the future of the Linux desktop will depend on porting the Android runtime to the desktop so that Android apps can run on the desktop.

honestly I'm just about done with Linux on the desktop. at this point there's no benefit to using it over MacOS, since the usable distros these days are just as much corporate-sponsored walled garden spyware. all the enthusiasts who used to make desktop Linux interesting have long since moved to MacOS.

>>3

Yeah. I used to be a diehard GNU/freetard but now I’m a macfag. With homebrew, iTerm2, gnu coreutils, binutils, moreutils, zsh, oh-my-zsh, git, etc you get similar functionality to Linux, but with support for a lot of software that doesn’t run on Linux. Sure, WINE and VMs are a thing, but it sucks compared to native Mac apps. Oh, and you can only run Xcode (and IB and simulator) on macOS. It’s really the best development platform at the moment. But who knows, that could change in the future. macOS has been playing second string for a while. Apple gives iOS all the attention these days.

Meanwhile, Gtk 4.0 will not be the final stable API of what we would call “Gtk 4”. Each 6 months, the new release (Gtk 4.2, Gtk 4.4, Gtk 4.6) will break API and ABI vs. the release that came before it. These incompatible minor versions will not be fully parallel installable; they will use the same pkg-config name and the same header file directory. We will, of course, bump the soname with each new incompatible release — you will be able to run Gtk 4.0 apps alongside Gtk 4.2 and 4.4 apps, but you won’t be able to build them on the same system. This policy fits the model of how most distributions think about libraries and their “development packages”.

And the mistakes of KDE 4 are repeated. You can't just redefine the semantics of version numbers like this. Why do the GNOME crowd always think conventional wisdom doesn't apply to them?

The lack of support parallel installs is just obnoxious, too. This ends with every app bundling whatever shitty old GTK point version it started with some years ago, and all its dependencies, together in a Flatpak. Forever. Maybe that is actually the goal now and they just don't want to come out and say it.

>>3
The Android API is a shit show as well. If it weren't 80% of the mobile market, nobody would put up with it, either.

>>1
IHBT. This proposal was withdrawnd replaced with this:

https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-promise-in-gtk/

So the .0 version madness was fixed, at least. It looks like development releases still aren't parallel installable, but at least it's more obvious that they actually are development releases.

Still using GTK 2 and have no intention of changing this. Time-scheduled releases are complete and utter idiocy that exists solely to create jobs for the development team. What a coincidence that just about anyone close to the freedesktop.org fucks loves them.

>>3
Get out, Miguel.

the future of the Linux desktop

kek