4 ms·
If you get confused by it then that's all that needs to be said. The rest has been discussed over and over. I've dropped Qt for other front-end tech and I'm hap
by joezydeco 1y ago
If you get confused by it then that's all that needs to be said. The rest has been discussed over and over. I've dropped Qt for other front-end tech and I'm happier now.
- CoastalCoder 1y agoI'm curious what you settled on and why. Care to elaborate?
- ogoffart 1y agoNot OP, but some users migrated from Qt to Slint and are happy with it. [https://slint.dev https://slint.dev] (I'm one of the Slint developers.)
- joezydeco 1y agoI'm rooting for you guys. Keep going!
- joezydeco 1y agoI work on equipment that can't open itself under LGPL3 rules. So I had to stop Qt use at 5.15, which went under maintenance support over 3 years ago. I've switched to vanilla web technologies. Node, React, etc. It's painful and it sucks but hardware keeps getting faster and cheaper. I can find contractors easily and I don't need an increasingly expensive subscription^H^H^H^Hcontract with Qt to keep my developer seat hot. They tried multiple times to get me to abaondon my Qt5 license to switch to their new revenue model. I told them to fuck off.
- HeyLaughingBoy 1y agoReplying to this post because the thread's getting too deep. What was painful about switching to web tech for UI? I've proposed it at work a few times for exactly the same reasons: get away from Qt and ease of finding developers. Since our GUIs all run on Linux (we usually do the realtime stuff on an external ARM processor) it seemed like an easy transition, but I've been shot down every time. Would be nice to hear what the downsides are.