Skip to content

Comment on GIMP developer looking for funding

Comments

I hope Gimp will switch to GTK3 at last. It's one of those projects that's still stuck with GTK2. Or even better - Qt ;)

Switching to Qt would be a bit ironic. Isn't Gimp the origin of GTK, aka the Gimp Tool Kit?

Indeed, that's why I added ;).

Yeah, I have very poor experience with my tablet in gimp on Windows and found in the bug tracker that plans to address it are on hold until the gtk3 port as apparently gtk2/wacom/windows doesn't work too well.

Their Roadmap and 2.10 changelog says they plan to release 2.10 with full GEGL integration http://wiki.gimp.org/wiki/Release:2.10_changelog / http://wiki.gimp.org/wiki/Roadmap#GIMP_2.10 and then the next version, 3.0 will be GTK3.

I'm so glad that Qt is gaining wider adoption in a post-GNOME world. It seems that everyone went Gtk because Gnome was the default DE for most major distros. With that constraint virtually gone, Qt has seen much wider adoption, which is awesome, as it is, in my opinion, clearly the superior platform.

> It seems that everyone went Gtk because Gnome was the default DE for most major distros.

No, the problem was with Qt itself. The whole reason GTK was created, is because Qt wasn't really FOSS. Only much later Qt was really opened up. So yeah, today Qt is open and it's clearly much better. But the damage was already done, and the split happened.

Qt has been open source since 1999 and GPL-licensed since 2000, nearly 17 years. GNOME was started in 1997 and GNOME 1.0 was released in 1999. So, much later is not really an adequate description.

I think the grandparent is definitely right. A lot of projects were started post-1999, when Qt was already open. But GNOME was the default desktop of many distributions (including Red Hat and later Ubuntu). Moreover, it is harder to bind Qt in order languages, since it is C++. There was a strong dislike for C++ in parts of the FLOSS community.

Not much, but 2 years were still enough to cause a major split and kick off Gnome / GTK and push the later from an obscure library used by Gimp to a widely used GUI toolkit.

GTK3, maybe, but QT? Yeah, you and the dude who barged onto the PostgreSQL hackers mailing list and tried to talk the community into rewriting the project in Rust should hang out.

"You should completely rewrite this project, consisting of hundreds of thousands of lines of code that people have worked on for years, using the tools I like better!"

Is this what you're talking about? https://www.postgresql.org/message-id/CAASwCXdQUiuUnhycdRvrU...

Because that's pure gold.

Or this one: http://www.wilfred.me.uk/blog/2017/01/11/announcing-remacs-p...

For extra enjoyment, look at the way they convert a function definition to Rust. You'd hope that the new version would be at least somewhat nicer than the original, but of course not. As lng as it's Rust it must be better, right?

GTK3 is years behind Qt in features. And I doubt it will change. So, I'd recommend to use it instead of GTK to everyone. The only issue with it, it's in C++, and bindings with C++ from other languages is a huge pain if possible at all.

It's possible. See e.g. Wireshark. But it is a pain.

I agree, but it's worth doing it.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.