←back to thread

250 points pabs3 | 5 comments | | HN request time: 0.8s | source
Show context
tombert ◴[] No.45123598[source]
I have never played with GNUStep. By the time I actually started real work as a professional software person (2011) it was already kind of considered a joke, so I never bothered learning how to use it.

It bothers me a bit, though. Developing for desktop Linux is still a pain in the ass, and I really wish the Linux community had agreed on One Desktop Framework To Rule Them All, and I think GNUStep could have been that framework if the community had been willing to embrace it.

replies(6): >>45123922 #>>45123951 #>>45124102 #>>45124494 #>>45125904 #>>45127032 #
1. bigyabai ◴[] No.45124102[source]
> Developing for desktop Linux is still a pain in the ass

GNOME works great if your language has good bindings for it. Qt is a bit more iffy but still usable if you need cross-platform.

replies(1): >>45124211 #
2. deaddodo ◴[] No.45124211[source]
I would argue that it’s heavily in the other direction, having developed fairly extensively in both.

The QT Linux ecosystem is far more cohesive and consistent and QT apps work more seamlessly between KDE, Windows, and MacOS. In my opinion, at least.

replies(2): >>45124376 #>>45126933 #
3. smaudet ◴[] No.45124376[source]
Agreed. Qt, for all it's flaws, focused on cross platform. Despite getting sold/resold nearly to oblivion, it had a commercial end (some paying customers), and so it received a level of polish that gtk just never did.

Not to mention, when the gtk3 devs went off the deepend, completely broke backwards compat so they could try some new UI...and you couldn't consistently run gtk on Linux...

replies(1): >>45125191 #
4. silon42 ◴[] No.45125191{3}[source]
I wish there was a good Rust binding for classic Qt...
5. cosmic_cheese ◴[] No.45126933[source]
It only having first class bindings for C++ and Python is a problem for a lot of folks, though. Plenty don’t want to write either.