3 ms·
All of this is pretty much how I feel on the matter, too. GTK3's interface was a really lovely blend of skeuomorphism and more abstract widgets that came togeth
by smoldesu 5y ago
All of this is pretty much how I feel on the matter, too. GTK3's interface was a really lovely blend of skeuomorphism and more abstract widgets that came together to make a really unique experience. Even if it didn't work in every context, I appreciated how well it worked for less complicated applications and making great-looking, device-agnostic GUIs. Cawbird was a wonderful native Twitter app made possible with GTK3. Curlew packed all of the important features of Handbrake/FFMPEG into a more streamlined, simple package. Foliate took e-book reading into the 21st century. So many amazing apps were enabled with this switch, and even though it's still a second-class toolkit, it was my guilty pleasure on Linux.
In comes GTK4. Much like the article alludes to, the elegant and simple shadow of interactive elements goes poof. Developers spend hundreds of hours crusading against letting people use third-party themes, just so they can simplify and reduce UI elements to a nigh-unusable pulp. Developing with GTK4 is a nightmare. Using GTK4 is a pain in the ass. For christs sake, there was a devastating font-rendering glitch that existed for more than ten months after the first GTK4 release that was ignored in lieu of simplifying buttons, developing a new forced stylesheet and telling people "don't theme our apps!" Whenever I take this up with a maintainer, they immediately take it personally and write out a litany of reasons why I'm wrong and why I'm not allowed to disagree. The priorities here are almost unbelievably misaligned, I've pinned my GTK packages at the last GTK3 release and await some sort of admission of failure.
I simply can't take it anymore. These are the people making desktop Linux miserable, and I frankly feel no remorse watching their attempts at "simplifying" the ecosystem crash and burn.
- MartijnBraam 5y agoThis is exactly how I feel about it. The sad thing is that if the whole gnome ecosystem burns down I'd have to use the alternatives that I like even less. I'm just not designing gtk4 apps untill it's actually better than gtk3
- smoldesu 5y agoDefinitely. Keep on trucking, I'm developing GTK3 apps right alongside you!
- throwaway82652 5y agoI'm sorry but most of this comment is a lot of nonsense. You're certainly allowed to disagree, but when you approach people with comments about their own work that are factually wrong, you'll get corrected. You're confusing those two things and taking it personally and that's a terrible mistake. Don't do that, it hurts you and it hurts everyone else around you. Just to clear up any confusion: - People have been working on the font glitch for the last ten months. It's not easy and the solution is not straightforward. Multiple solutions have been proposed but none are without issues. The problem is not being ignored. I want it to be fixed too. - The choice of whether to allow themes or not belongs to the app developer. This hasn't changed at all from GTK3. When making an app, you can choose to allow themes or not. Some app developers won't, but you don't have to make that choice. - The stylesheet isn't forced at all, when you develop an app you can configure your styles to always override the platform theme. This also hasn't changed at all from GTK3 and doesn't change with libadwaita. Take a look at the style context priority system for more info. - Pinning your packages to GTK3 in protest doesn't help you. It doesn't make a difference to the GTK developers at all. If you want to make use of some GTK4 features eventually, it would be best to start working with it and getting your issues sorted out now. You can ignore what the other app maintainers are saying, that has no effect on you. Hope that helps, thanks.
- smoldesu 5y agoOh good, I always look forward to condescending GNOME apologists to reply to my comments. Let's disseminate this comment and use it to help understand why me, OP, and hundreds of other people in this thread are frustrated with the state of GTK and GNOME right now: > People have been working on the font glitch for the last ten months. It's not easy and the solution is not straightforward. Then why was it working fine in GTK3? Sounds to me like someone made a breaking change, and didn't anticipate the consequences. The solution is to roll things back or wait until this new implimentation is fixed to push the code to actual users. Unfortunately, the GNOME developers are more interested in scorching earth than they are in maintaining a well-made desktop. Oh, and it's not because it's a "hard issue" to fix, it's because nobody made a PR for several months. Apparently none of the core maintainers considered it much of a problem. > The choice of whether to allow themes or not belongs to the app developer. This hasn't changed at all from GTK3. No, it doesn't. There is not a single application written with GTK3 that can stop me from changing it's theme. I'm sorry if you disagree, but that's just an outright lie (I say this as someone who actually writes GTK3 code). > The stylesheet isn't forced at all, when you develop an app you can configure your styles to always override the platform theme. ...and I can override it again. Any questions? > Pinning your packages to GTK3 in protest doesn't help you. Correction, it doesn't help you. It keeps my applications looking just fine. > It doesn't make a difference to the GTK developers at all. That seems to be a recurring trend when negotiating with GNOME/GTK developers. I don't care, I'm perfectly satisfied taking matters into my own hands since they'll ignore me anyways. > If you want to make use of some GTK4 features eventually, it would be best to start working with it and getting your issues sorted out now. I don't. What features are there, right now? Worse text rendering? Less accessibility features? More extreme, abrasive maintainers and fewer people writing code? A worse native experience, more middleware and less software freedom? Less native packaging? More Flatpak bloat? Worse touchscreen compatibility and an increasingly fractured codebase? More broken custom widgets that don't adhere to the GNOME HIG? An uglier, flatter overall design philosophy? Militant users and developers who hunt people down when they express their feelings about software they used to use on Hacker News? Worse looking buttons? You can keep it. > You can ignore what the other app maintainers are saying, that has no effect on you. I don't even know what you're trying to say here, but it sounds like doublespeak. This entire comment does, actually, and I'm not sure what your goal was by posting this. Nothing you've said accurately describes the reality of using GTK applications, it's more like an idyllic reflection of what people think the ecosystem should look like, ignoring everyone who doesn't throw away their current workflow to live in GNOME-land. Unless you start acknowledging the pragmatic reality of GTK's end-users, GNOME will continue to hemorrhage maintainers and stir up unnecessary and counterproductive drama for the sake of a few people's ego. And to think that what I said was nonsense, get a grip...