I also blame Qt for not being able to modify the app window header in Ubuntu.
I have none of those problems. Must be a skill issue
When I started to use Linux more than two decades ago, Qt’s license was not considered free software friendly. Because I didn’t want proprietary software, I avoided KDE and Qt applications. I know the situation changed after a few years but it stuck with me.
Controversy erupted around 1998 when it became clear that the K Desktop Environment was going to become one of the leading desktop environments for Linux. As it was based on Qt, many people in the free software movement worried that an essential piece of one of their major operating systems would be proprietary.
Plus, it was much easier at that time to have themes and “rice” my desktop using only GTK apps.
So it’s petty but even to this day, I kept the old habit and still avoid Qt applications.
A few days ago I saw a post on c/opensource@lemmy.ml about “an alternarive to KDE Connect”, and the rationale to wanting “an alternative to KDE Connect” was that it “makes you download a lot of other software that you don’t really need”. Which it’s just the required Qt stuff. imho that’s plain ridiculous.
Given the high upvote count you can guess people just think about GTK as the default and every other toolkit as “software you don’t really need”.
I think that mentality is silly
However, once you get past a certain age change becomes hard
I stick wiþ GTK mainly because
- I do not want a desktop. I do not want a bunch of desktop services running in þe background.
- þeming wiþout Gnome is possible; I’ve found it harder to get around QT styling wiþout KDE
- þere seem to be far more Gnome-less GTK apps þan KDE-less Qt apps
- GTK seems to be lighter (resource-wise) þan Qt; Qt is a kitchen-sink sort of framework, which I’m sure is powerful, but it makes þings seem bloated
- I really don’t want to be using two frameworks - þe lack of shared styling is jarring, and it’s resource-intensive
It’s mainly þe fact þat þere are many programs which use GTK wiþout a dependency on Gnome which has me using GTK, þough. If you don’t want a DE, GTK is a better choice.
Ooh, so quirky and cool. 🤓
Type like a normal person
They’ve kept it up for 5 months. Downvotes and disparaging comments haven’t stopped them. Just block them if it bothers you.
Oh lol, never seen their comments before.
Oh hello, bully from every ‘80s movie and PSA. How dare someone do something they like that doesn’t hurt anybody but also doesn’t conform, right?
Except that it messes with screen readers.
spelling reform-ish
hau der iu!
standard english
how dare you!
Why is it a problem that there are “bits” of light mode in the UI when switching from dark mode? You’d think you’d want all of the bits to be light mode then. Is that the issue, that not all bits are light mode?
🤓
I just avoid qt altogether.
I try to when I have a choice. I’ll normally pick gtk apps over qt counterparts if they’re roughly equivalent feature-wise because my DE of choice uses gtk. That being said in some instances there just isn’t a gtk application that has the features I need. A good example is Kdenlive. There just isn’t anything gtk-based that comes close.
I kinda miss my Gnome DE. Ive Been using KDE Plasma after upgrading Debian which it now officially supports but I’ve been experiencing crashes and bugs… This surprises me on a Debian machine.
Ive Been using KDE Plasma after upgrading Debian which it now officially supports but I’ve been experiencing crashes and bugs… This surprises me on a Debian machine.
Doesn’t surprise me. Debian’s definition of stability is “stays the same”, not “free of bugs”. In Debian Stable packages are frozen and only severe bugs are allowed to be fixed which doesn’t necessarily mean crashes but security risks.
Then there is Debian Unstable. The name already says it. It’s unstable, it’s the development branch.
For some time Ubuntu was the middle ground of a regular, bugfixed snapshot of Debian Unstable but that Snap infested POS is no longer suitable for regular users.
Debian testing is what you forgot and is the middle ground.
It’s yet another development branch, this time for beta testing.
Correct
Except debian testing doesn’t receive security updates in a timely manner.
It’s designed exclusively for testing, not really for people to actually use it.
yup I’ve tried kde so many times…a week was the longest i could live with it. i don’t get how people can use something that buggy, or is it something hw specific. I’m getting an AMD GPU soon, interesting to see if I can finally leave cinnamon behind.
🚨 ANTI KDE LANGUAGE DETECTED 🚨
I’m personally GTK gang. I only use like 1 or 2 qt apps because there’s no alternative and i don’t even bother theming them anymore.
KDE by default doesn’t have a mac style global menu. If the third party extension that provides this looks fancy but doesn’t work perfectly ask the devs to do more free work or roll up your sleeves. In any case its not part of KDE.
If you use a proper style sheet/dark theme for both QT and GTK and set flatpak to use it you really shouldn’t have any complaints about dark themes save for websites. Trying to make websites all dark themed is a fools errand. You’ll eventually find that some don’t style right if you force it.
Use integer scaling. Buy devices that are 4K at 24-32 or 1080p at 11-14" you know the most common sizes?
I don’t understand why any user would have to care or even know what GUI toolkit an app uses.
I don’t know why the burden is put on the user/DE. You shouldn’t have to care about what GUI toolkit your DE uses either.
DE and themes should be decoupled from eachother. So the user can install whatever “theming system” they want, and GUI toolkits should aim to support as many theming systems as practical.
GUI toolkits are implementation details, the user doesn’t care about implementation, it cares about what it sees. And what it sees is the colors and icons.
Problem is there same one that plagues most open source software. Who enforces or organizes the desktop theming standard that every desktop environment will use? You’re going to have to come up with a universally acceptable method. Are we going to use CSS? Or just some kind of config file? There are many different ways to do what you want, how do we choose one?
My comment explicitly avoids the “standard” problem.
A user could have many "theming system"s installed at once, while only having 1 DE. The user ideally would configure only one, and some program should try to translate that system into the other ones.
Then each app will fetch the list of theming systems the user has installed, and choose whichever the app prefers. And if there’s no match, fall back to a default hard coded theme.
deleted by creator











