Hacker News new | past | comments | ask | show | jobs | submit login

(At Remotion) We decided against Qt partially based on my experience working on the Dropbox desktop client—Qt sounds great in principle but in practice we think you're better choosing between native or web tech. I'm less familiar with GTK.



You'd rather miss out on 95% of the desktop market than use Qt?


Qt is a particularly poor experience on macOS. Also the past few years all the new stuff in Qt was QtQuick, which seems basically like JS, and if you're into JS, why not just use Electron?

GTK is a non-starter for something professional, at least if the experiences of the GIMP and Inkscape on macOS are representative. (Also, it's C, which does avoid some ABI problems, but it's hardly suited for an object-oriented environment)


GTK is using GObject to retrofit objects into C and actually maps pretty well to OO languages because of that.


False dichotomy—in our case we’d rather _start_ on macOS and then build other platforms separately… than use Qt.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: