News for hackers. Stuff that matters.
Re:GTK 3.99 by ohazi on Friday July 31, 2020 @05:11PM (#24014160)
Is GTK 3 -> 4 expected to be as big a clusterfuck as 2 -> 3?

I'd really rather not go through all that again.

Re:GTK 3.99 by quotemstr on Friday July 31, 2020 @06:37PM (#24015043)
The GTK 4 transition is totally unnecessary. Any new functionality needed can be incorporated into the existing API in a backwards-compatible manner. Major version bumps should be an absolute last resort, not something a major infrastructure library does when it gets too stable and its developers get bored.

You want a new recyclerview-like list widget? Great. Make a new damned widget. You want a retained-mode rendering system? Great! Add a bunch of new widget hooks. Don't require a whole new major version bump and make everyone using GTK3 deal with dependency hell trying to get upgraded. It feels like only yesterday that most things finally moved off GTK2.

There is ZERO reason for an ABI break here. None. GTK3's ABI is a perfectly adequate base for adding new functionality. The GTK people, by making a GTK4, made a lot of work for everyone for no benefit.

Is the GTK4 API cleaner? I guess? Event objects are opaque now. There's no root window. Yay? But "it looks slightly cleaner" is a totally inadequate justification for the pain of yet another GTK ABI transition.

I could go and on about how much gratuitous breaking changes piss me off.

The same goes for Wayland, by the way --- X11 has an extension mechanism. Wayland could have used it. And don't tell me about the core protocol breaking the model --- it doesn't hurt anything if you don't use it.

Re:GTK 3.99 by moonchild on Friday July 31, 2020 @06:58PM (#24015251)
X has serious architectural problems. What would it mean to build a completely new windowing API using the extension system, if 'proper use' would mean using exclusively the new extended API? Is that meaningfully different from or better than building a new windowing system (cf wayland) and implementing x11 on top of it (cf xwayland)?

FWIW, I think wayland also has serious architectural problems, and see arcan as much more promising, but rewriting/replacing legacy can definitely be justified. Extension hell is much worse than compatibility hell. If you don't like gtk4's api, then don't use it; gtk3 will continue to work. It's better that an api should be coherent and cohesive than that it should bend over backwards to keep compatibility with ideas that no longer make sense. Obviously, this should be applied within reason—don't do a complete rearchitecture every month—but compatibility breaks are important and necessary.

Re:GTK 3.99 by quotemstr on Friday July 31, 2020 @07:01PM (#24015289)
> if 'proper use' would mean using exclusively the new extended API? Is that meaningfully different from building a new windowing system (cf wayland) and implementing x11 on top of it (cf xwayland)?

We're already in a world where "proper use" of X11 means relying on ubiquitous extensions. Nobody uses the core font rendering APIs anymore --- instead, everyone uses fontconfig and XRENDER. The transition was gradual and smooth. Nobody had to rewrite applications. Both old-font-API and new-font-API X11 applications shared the same X server, the same connectivity configuration.

The transition to Wayland should have looked like a super-XRENDER, not some bespoke new thing with an embedded X server that will always be a second-class citizen just like embedded X servers on Windows and macOS are.

Making some grand new thing and emulating the legacy thing is harder to get right than just teaching the legacy thing to do something new. Why? Because in any rewrite, you not only have to rewrite the parts of the old system that are bad, but also the parts that are good.

Re:GTK 3.99 by ATsch on Saturday August 01, 2020 @03:59AM (#24018630)
Yet the people who were working on Xorg decided to write wayland instead. Why? Because there was little more benefit to he had from the previous approach. Xorg had become a slow and bloated synchronous IPC service and replacing it with a UNIX pipe was the logical solution.
Re:GTK 3.99 by quotemstr on Saturday August 01, 2020 @04:18AM (#24018727)
> Xorg had become a slow and bloated synchronous IPC service and replacing it with a UNIX pipe was the logical solution.

You do realize the the X11 server connection is also almost always a Unix socket, right? (ITYM "Unix socket", not "Unix pipe".) That's like showing out your spork and replacing it with a spork.

> Yet the people who were working on Xorg decided to write wayland instead.

My whole point is that they were wrong to do so, just like I think the GTK people are wrong to break ABI on GTK4.

Re:GTK 3.99 by ATsch on Saturday August 01, 2020 @11:36AM (#24021264)
A completely new solution was inevitable because there was nothing more that could be done with Xorg. All of the complexity that mattered had moved into the WM, Compositor or Client. It wasn't actually doing anything anymore.
Re:GTK 3.99 by quotemstr on Saturday August 01, 2020 @12:50PM (#24021909)
> A completely new solution was inevitable because there was nothing more that could be done with Xorg.

I see no evidence behind this assertion. What specifically would have prevented the further evolution of Xorg?

> All of the complexity that mattered had moved into the WM, Compositor or Client.

Good. So that means that Xorg didn't have to change very much. All Xorg had to do is provide mechanism, not policy, and let WM, compositor, and client cooperate as they've been doing for decades.

But instead the Xorg maintainers got bored and decided to make a big ball of mud with no separation of concerns.

Re:GTK 3.99 by war1025 on Friday July 31, 2020 @06:44PM (#24015114)
> The same goes for Wayland, by the way

Wayland happened mainly because they could get to 90% of Xorg functionality easily and ignored the fact that the last 10% would take over a decade to achieve parity on.

Re:GTK 3.99 by quotemstr on Friday July 31, 2020 @06:46PM (#24015130)
> Wayland happened mainly because they could get to 90% of Xorg functionality easily

We're at 12 years of Wayland and counting and the thing still isn't really usable outside a very narrow use-case. I still run X11 myself and will for a long time. As far as I'm concerned, Wayland has set free software windowing back by a decade. After all this time, Wayland still isn't at parity with X11 even for use cases that Wayland intends to support --- and some things that X11 can do are non-goals for Wayland and will never be supported. What exactly is so compelling in Wayland that it was worth putting progress on hold since 2008?

Yeah, yeah, I get that Wayland has a nice buffer-based composition system. So what? Whatever Wayland does, it could have done over an X11 extension.

Re:GTK 3.99 by sjy on Friday July 31, 2020 @09:50PM (#24016614)
Wayland was the default in Ubuntu 17 and is still the default in Fedora. I like it because dealing with multiple displays and tearing under X annoys me more than dealing with screen capture under Wayland. “Not really usable outside a very narrow use-case” overstates the problem.
Re:GTK 3.99 by fmntf on Friday July 31, 2020 @06:54PM (#24015208)
While I totally agree with you in a desktop-like scenario, please note that X is totally inadequate and bloated for other domains (e.g. automotive).
Re:GTK 3.99 by rleigh on Friday July 31, 2020 @07:12PM (#24015388)
As the other poster mentioned, X11 used to run on really old resource-constrained systems. Nothing about it precludes using it for embedded automotive applications. A tiny MCU could manage it. The MCUs used for current automotive stuff are powerful enough to run Linux with Vulkan for crying out loud.

Though I think for many of these embedded applications both X11 and Wayland are overkill when EGL direct works just fine. A full windowing system is massive overkill.

Re:GTK 3.99 by quotemstr on Friday July 31, 2020 @06:55PM (#24015219)
Why? X originally ran on machines far less powerful than even the shittiest automotive head units around today.
Re:GTK 3.99 by stonogo on Friday July 31, 2020 @07:12PM (#24015390)
Because the problem isn't with X, it's that all the toolkits people want to use were written basically to use X as a glorified framebuffer. Wayland is a reorienting of the underlying stack to accomodate this. You could absolutely make an automotive stack with something like X and Motif, but nobody in the industry really wants to use those tools.
Re:GTK 3.99 by asveikau on Friday July 31, 2020 @08:14PM (#24015966)
Nokia n900 had a touch screen smartphone UI based on gtk with X, with a 600mhz arm core and 256mb ram. I had one. It was pretty good.
Re:GTK 3.99 by owl57 on Friday July 31, 2020 @10:16PM (#24016775)
I turned my N810 on recently and played a bit, so I can compare it directly to modern devices. "Pretty good" is a big understatement.
Re:GTK 3.99 by edsac_xyzw on Sunday August 02, 2020 @02:14AM (#24026730)
Most embedded graphical Linux applications don't use X (X Windows System), instead they use framebuffer directly or any library such as Qt Widgets or QtQuick/Qml that draws on top of the framebuffer device file. So, there is no need for developing a new Window system that can work on both Desktop or embedded systems.
Re:GTK 3.99 by metroholografix on Friday July 31, 2020 @08:34PM (#24016099)
Back in the day, I used to run XFree86 on a Pentium 150 with 64MB of RAM and an S3 Virge graphics card.

Don't tell me that X is bloated.

Re:GTK 3.99 by hedora on Friday July 31, 2020 @11:49PM (#24017336)
I ran it on a 386/25MHz, 8MB of RAM. It was much faster than Windows on the same machine.

Enlightenment was fast on that machine. The desktop switcher in the panel had old-school desk lamps pointing at the active desktop.

I miss that theme, and I can’t find any screenshots.

Re:GTK 3.99 by fulafel on Friday July 31, 2020 @09:24PM (#24016426)
Before that, 8 MB was iffy, 16 MB good in the early Linux days.
Re:GTK 3.99 by michaelmrose on Friday July 31, 2020 @07:33PM (#24015616)
Making life easier for Ford sounds like a low priority goal.
Re:GTK 3.99 by AlexMax on Friday July 31, 2020 @10:03PM (#24016694)
> We're at 12 years of Wayland and counting and the thing still isn't really usable outside a very narrow use-case.

Must be a wide narrow you're talking about. I've been using it as my default session across two different distros and the only problem I can recall having was strange mouse-grabbing behavior in Firefox, and I don't even think that was Wayland's fault.

Re:GTK 3.99 by war1025 on Friday July 31, 2020 @07:06PM (#24015332)
I also still use Xorg and can't really think of a scenario where I'd switch.
Re:GTK 3.99 by dilandau on Friday July 31, 2020 @08:34PM (#24016103)
This is the comment I wish I had made. The transition from 2 to 3 was terrible for end users, distros, and app developers. I wonder if redhat is trying to embrace/extend/extinguish because it's impossible for me to see gtk (and gnome) teams actions as anything less than overtly hostile.
Re:GTK 3.99 by cycloptic on Saturday August 01, 2020 @12:29AM (#24017630)
Please don't. It's getting rather boring to see the baseless conspiracy theories that show up whenever an article is posted about gtk, gnome or systemd. Apparently they're trying to embrace extend extinguish their own business now?
Re:GTK 3.99 by dilandau on Saturday August 01, 2020 @07:27AM (#24019623)
When 1 company is responsible for the most cancerous, complicated, baroque, developer-hostile libraries? I think it's fine to ask these questions.

Would you create a new open-source desktop application using gtk4? Would you want to package and maintain systemd/pulse/etc?

Also: why are you responding to all the critical comments in the thread, and writing dismissive replies?

Re:GTK 3.99 by cycloptic on Saturday August 01, 2020 @08:25AM (#24019940)
Please don't make these inflammatory comments either, it adds nothing to the discussion. You're in the thread of a GTK release announcement making these comments, I'm not sure what you're trying to accomplish but I doubt it's going to be constructive. I've used GTK for a few projects, it's not perfect but the conspiracy theories and aggression are unwarranted. Nobody is out to get you. At worst, as a developer you can ignore it and use Qt instead and it won't affect you.

Personally I would rather make a new toolkit, but it takes many years and many contributors to make a decent one. GUI toolkits are a complex business. Don't discount the amount of work that was already done on GTK or Qt, there are some serious lessons you can learn from those codebases.

Re:GTK 3.99 by hedora on Friday July 31, 2020 @11:38PM (#24017236)
Agreed.

Also, systemd seems similarly hostile and is also from redhat.

Wayland... does seem to be solving some real problems, but the transition hasn’t been going well either.

Re:GTK 3.99 by jiqiren on Friday July 31, 2020 @07:03PM (#24015311)
This makes me feel old. I got fed up in university submitting app patches using GTK in ~1999.

Still hasn't been improved in 20 years? sad.

Re:GTK 3.99 by dekhn on Friday July 31, 2020 @07:20PM (#24015476)
I used tkinter in 1999, gtk by 2006, and switched to qt a few years ago. I love qt.
Re:GTK 3.99 by axaxs on Friday July 31, 2020 @07:31PM (#24015596)
Same path for me. Although I use Gnome and despise KDE, QT is far superior to GTK in my opinion.
Re:GTK 3.99 by dilandau on Friday July 31, 2020 @08:41PM (#24016157)
I still use tcl/tk and it's still the best choice for apps of modest requirements, in my opinion.

It's stable (unlike gtk), and truly free (unlike qt, which is also a c++ behemoth). It's utterly simple and elegant.

Re:GTK 3.99 by nfoz on Friday July 31, 2020 @05:27PM (#24014369)
What were the problems with this transition?
Re:GTK 3.99 by madboston on Friday July 31, 2020 @05:36PM (#24014481)
There are not enough words I can write for this.
Re:GTK 3.99 by rleigh on Friday July 31, 2020 @07:39PM (#24015671)
There are so many that I could spend several hours ranting about them.

If you invested time and effort in writing GTK+ 2.x applications, the GTK+ developers spent zero time caring about API compatibility even for cases where it would have cost them nothing to maintain. They just had to rip it all out just for the sake of it, even when single line compatibility forwarding functions would have been entirely sufficient to avoid breakage.

This is the fundamental dichotomy with GTK+. Its developers want to hack on the toolkit itself for their own amusement and occasionally for GNOME features. They don't care about the needs of the application developers who would use their toolkit to write actual applications. God forbid it's used for its intended purpose. If you invested thousands of hours into using it, they will not bear that in mind as they rip out stuff people used for over two bloody decades in the name of "progress". Like GtkHBox. Gone. There since 1997 and used by every GTK+ application on the planet, but that's no reason to keep "old code"!

That's their choice. But other libraries like Qt do take better care of the interests of their customers and end users, and don't gratuitously break core functionality on a whim while chasing shiny new things. In the above example, the GtkHBox class is replaced by GtkBox with an "orientation" property.

Now, any sane developer would retain GtkHBox and simply implement it in terms of GtkBox with a defaulted "orientation" to horizontal. New way works. Old way works. No breakage. Everyone is happy. But they just had to rip it all out in the name of "progress". Consider how many instances of this there are in a large codebase. Hundreds to thousands in a big UI. The breakage was entirely avoidable and quite unnecessary. Maintaining the compatibility code would have been a tiny effort with a few one-liner compat functions, but ripping it out imposed huge problems upon every user of the library. "Cleanliness" needs to be traded off against "breaking end users", but they have the scale dialled all the way to one side, which is spectacularly unhelpful and inconsiderate.

That's just one class and one example. You could write a book enumerating all of the other instances. It's that bad.

No one who looks at this rationally in 2020 should be choosing GTK+ for a new project. You know in advance it will end in tears and frustration, as all of the value you created will be destroyed on a whim by developers who should know better, but go ahead and break everything anyway just because they can. That's their choice. But it's our choice to not get sucked into the bizarre world where this kind of software maintenance is considered in any way acceptable or justifiable. Seriously. These people are on another planet. What project intentionally gives the finger to all of their developer base? A really messed up one with nonsensical priorities.

Sorry if this comes over badly. If you can't tell, I've got a bit of pent-up frustration after spending far too many hours of my life trying to work around GTK+, submit patches which are ignored, and try to develop applications in spite of GTK+, not because of it. I should have just used Qt from the start.

Re:GTK 3.99 by cycloptic on Friday July 31, 2020 @07:58PM (#24015840)
>retain GtkHBox and simply implement it in terms of GtkBox with a defaulted "orientation" to horizontal.

I'm sorry, I understand your frustration but to me this is a terrible example and kind of makes the rest of your post look like complaining about a non-issue. This is exactly how it's already implemented in GTK 3. GtkHBox was deprecated there and slated for eventual removal, then it got removed in GTK 4 because the whole point of it is an API break and removal of deprecated functions. If this bothers you, you can keep using GTK 3 which is now considered feature-complete. The situation with GTK 2 was the same, you could keep on using it if you didn't want to bother updating your application.

Re:GTK 3.99 by rleigh on Friday July 31, 2020 @08:05PM (#24015901)
Wow, that response demonstrates exactly what is wrong with this library and its developers.

"You can carry on using the old version" is a real cop-out which does not address the substance of the complaint in any way whatsoever.

Yes, I know it's being removed in GTK+4. You didn't have to remove it. You chose to. And to hell with the consequences. You could have kept it pretty much indefinitely with near zero maintenance overhead if you cared about compatibility and the extent to which that core functionality was used.

I am always surprised at how much time gets wasted on trivia, and yet a simple maintenance issue like this is too difficult despite requiring much less effort.

Re:GTK 3.99 by chris_wot on Friday July 31, 2020 @09:40PM (#24016546)
Deprecated means “if you use this, on your own heads be it”.
Re:GTK 3.99 by rleigh on Saturday August 01, 2020 @05:22AM (#24019027)
Deprecation does not imply removal in the short-term. Java has deprecated many things which will never be removed, because they care about compatibility. Just because there's a newer way to do something does not mean the old way must be removed as soon as possible. If it was very high maintenance and it prevented the addition of new functionality, this might be justified. But that's not the case. It's completely gratuitous.

The GTK+ removals are akin to removing "strlen()" from the C library because a better "strlengh()" was added in the meantime. Compatibility matters. And well-maintained projects balance that with the addition of new features.

Re:GTK 3.99 by chris_wot on Saturday August 01, 2020 @10:11AM (#24020543)
Perhaps there should be a raft of functions in the C library that are deprecated and removed.
Re:GTK 3.99 by rleigh on Saturday August 01, 2020 @04:21PM (#24023580)
Deprecated, perhaps, should suitable replacements be standardised. Removed, absolutely not.

It cannot be overstated just how terrible compatibility breaks are. C is nearly 50 years old, and all of its standard functions are thoroughly entrenched, despite their numerous known defects. It took long enough to eliminate gets(), and that was broken from inception.

In almost all cases, removal is not the best solution. Supplementing with a safer or better alternative to supersede the original, by all means. But deliberate breakage causes nothing but pain all around.

In the case of GTK+, it's nearly 25 years old. These is a legacy of thousands of applications, large and small, which have invested hundreds of thousands of developer-hours in it. Obsoleting things might save the GTK+ developers a little extra effort (though I doubt this), but it imposes several orders of magnitude more work upon the worldwise developer base tied to GTK+, which could be avoided entirely without holding back progress.

Re:GTK 3.99 by chris_wot on Saturday August 01, 2020 @10:57PM (#24025958)
So you expect the developers to keep maintaining old interfaces forever? The C library, that I understand (POSIX and all), but GTK+? I think that's an unnecessary burden.

Now if someone wanted to make a shim library that had the old APIs, that might be doable.

Re:GTK 3.99 by rleigh on Sunday August 02, 2020 @05:00AM (#24027398)
It all comes down to impact.

Removing an unused and long-deprecated interface is low impact. Removing a widely-used interface is very high impact.

When you have an interface that is nearly 25 years old and a staple part of every GTK+ application in existence... that's a very high impact change. I'm unsure how the GTK+ developers rationalised that one. But I am completely certain they made the wrong call there. It's too disruptive. I don't think it should have ever been dropped, or considered for dropping. Deprecated, yes. But not dropped.

I'm coming from the perspective of an end-user of GTK+: an application developer. Though I have historically also contributed bits upstream. I moved away from using GTK+ several years back at this point, precisely because the upstream maintenance practices were too much of an ongoing imposition, along with all the other criticisms one can make of it. GTK+ might be "free", but the cost of using it is very, very high.

Re:GTK 3.99 by cycloptic on Sunday August 02, 2020 @10:58AM (#24029093)
There are 800 deprecated symbols in GTK 3. They were removed in GTK 4 because nobody upstream is willing to pay the cost to maintain them anymore. There is a real cost and typically this cost is that you have to commit to bugfixes and refactoring on the deprecated bits for the entire lifecycle of the new version, which is potentially many years. If the app developers aren't willing to pay the cost either, then you've got a hung jury situation.
Re:GTK 3.99 by cycloptic on Friday July 31, 2020 @08:22PM (#24016018)
I'm not a GTK developer so please spare me the shooting of the messenger. All I did was read their documentation. From what I've seen there are very few paid developers actually working on GTK. Everyone else is volunteers and none of them are interested in maintaining deprecated APIs for any protracted amount of time. Even with the removal of a lot of deprecated functions in GTK 4, there is still a ton of untested code sitting around that nobody really maintains. You're welcome to write tests for these and maintain an external compatibility layer yourself if you want, but it makes no sense to expect other volunteer developers to do this for you when the old versions are considered stable.
Re:GTK 3.99 by rleigh on Saturday August 01, 2020 @04:10AM (#24018692)
> "Everyone else is volunteers and none of them are interested in maintaining deprecated APIs"

This is a complete cop-out. It's maintained by several RedHat employees as part of their duties, and a handful of volunteers.

Every software project on the planet, including commercial ones, is maintained with limited resources. The amount of development and maintenance which is possible is constrained by the available developer hours, and work is budgeted based on that.

The cost/benefit of maintaining the compatibility code is so low that it's not even worth the effort to remove it. The time taken to drop it was likely on a par with the time to retain it. It was already written. But the cost imposed on all their userbase after removing it is absolutely huge. And it means that an application can't target old and new versions due to the break. That wreaks havoc with support lifetimes and imposes thousands of developer-hours of effort for porting. Lots of effort... just to get back to where you were. Unjustifiable.

I could understand if there was a huge benefit to be gained. But there isn't. And when you look at what they do spend their time on, so much is wasted on other activities that justifying its removal based upon developer resources wears a little thin. It's a weak justification which ultimately boils down to just wanting to, and completely ignoring the actual users of the library.

Re:GTK 3.99 by cycloptic on Saturday August 01, 2020 @08:03AM (#24019825)
If the cost/benefit is so low then you do it. I'm completely 100% serious about this, I assume you have some customers lined up who are willing to pay for this so just take the money and don't worry about what anyone else does. Make it as an external library so you don't have to spend time convincing upstream to merge and maintain it. None of the existing volunteers are willing to do this work, and the paid developers get paid to work on what Red Hat customers pay them to work on, which evidently is not related to maintaining legacy applications at all. If they want to leave money on the table, that's their problem. There is nothing wrong about what you're saying but it's mostly hot air, you're preaching to the choir here.
Re:GTK 3.99 by RedShift1 on Friday July 31, 2020 @05:52PM (#24014625)
API changes every minor release.
Re:GTK 3.99 by vetinari on Friday July 31, 2020 @06:09PM (#24014799)
Any specific examples?

According to https://developer.gnome.org/gtk3/stable/gtk-migrating-3-x-to..., the changes were pretty minor.

Re:GTK 3.99 by ohazi on Friday July 31, 2020 @06:41PM (#24015087)
They broke enough of the theming API on every minor release that for a few years it was essentially impossible to run any GTK theme other than the GNOME sanctioned default theme (Adwaita). Adwaita was updated in lock step with GTK minor releases (by the same developers), and unaffiliated theme builders were left with periodic drops of subtly different behavior and no notes or tools on how to update their themes. It drove many of them away.

This was apparently a part of a deliberate strategy around GNOME branding. The GNOME developers wanted all GTK apps to have one consistent look-and-feel, they wanted people to associate this look with GNOME, and they wanted people to start thinking of GTK apps as "GNOME Apps."

More recently, they crippled existing functionality for server side-window decorations in Wayland (which literally every other toolkit supports), because GNOME decided to use exclusively client-side decorations. They vetoed all of the reasonable seeming workaround proposals, essentially telling developers to either use GNOME's decorations or to manually draw the close/maximize/minimize buttons.

Honestly, all of the crap that systemd gets should be redirected towards GTK/GNOME. I've never seen a group of developers act in such bad faith.

Re:GTK 3.99 by p_l on Saturday August 01, 2020 @02:45AM (#24018255)
The GNOME/GTK devs and systemd devs are pretty tightly coupled... Recall the infamous config defaults change that killed sessions impacting things like tmux/screen? Pretty sure it was done because of gnome-session...
Re:GTK 3.99 by vetinari on Saturday August 01, 2020 @05:31AM (#24019070)
Theming is internal, not public API though. It is fine to break internal APIs, that's why they are internal.

Themers were warned, that the styling engine was under heavy rework. Gtk people could either wait few years until it's done and be stuck with Gtk2 meanwhile, or go out with Gtk3, which has relatively stable public API and internal API under rework. It's no brainer to take the same way they took. They also communicated this, so anyone who ignored their advice has no basis to complain. They were told exactly what is going to happen, and that they will either have to keep up, or not do it yet.

Switch to client-side decorations was also done for a very good reason. There's a post by Rasterman (author of the Enlightenment WM) on reddit, where he details it why - and he is not even associated with Gnome. Windows and Mac also do client-side decorations, you just cannot see it, because clients cannot connect directly to the compositors, they have to use the client side libraries that handle that. Which is exactly what Gtk does.

Re:GTK 3.99 by nyanpasu64 on Saturday August 01, 2020 @01:22AM (#24017886)
One time GTK3 altered the CSS formatting, causing Java Swing delegating theming to GTK3 to have invisible checkboxes and other widgets.
Re:GTK 3.99 by saagarjha on Friday July 31, 2020 @06:56PM (#24015236)
Looks like they got the worst of both worlds, with no Cocoa arising from it and a bunch of pissed off developers and users…
Re:GTK 3.99 by baybal2 on Friday July 31, 2020 @07:32PM (#24015609)
I myself was turned off from working on GTK+ when it became clear that GTK is turning from "The Gimp Toolkit" to "The GNOME Toolkit"
Re:GTK 3.99 by wolfgke on Friday July 31, 2020 @06:41PM (#24015088)
RedShift1:

> API changes every minor release.

vetinari:

> the changes were pretty minor.

Was this pun intended? ;-)