Comment by Palomides
6 days ago
Qt with QML for a somewhat embedded use case. I think it hits a really nice intersection of native speed, GPU acceleration, interfacing with C++, and ease of development.
I wouldn't really recommend a career out of it.
Qt used to be what I used as well, but the licensing has become so repulsive for professional use that I now refuse to touch it now (not even for my open source side projects where this wouldn't be an issue).
Too bad the hopes from the early Nokia adoption days got smashed by MS mole Elop and the later owners of Qt.
Yeah, it's quite sad to see Qt on the N9 and, now, on SailfishOS.
We were robbed of a future with lightweight and responsive native apps. Android pales in comparison.
I have a small business license which I use for developing 3 commercial application. It is ~$1000 per year and the licensing seems quite reasonable.
why are you paying for a license? are there non-LGPL features you're using?
1 reply →
The licensing barely changed, the only change is the scare tactics of the Qt Company. The only thing to do is not to get scared by such legally meaningless noise.
We have no issues shipping both FOSS (LGPL) and proprietary solutions using Qt without having to pay any license fee... not sure what issues you're running into.
> using Qt without having to pay any license fee...
Would you mind elaborating which Qt editions, linking etc. you use?
1 reply →
> I wouldn't really recommend a career out of it.
Care to say why? I ask because that's what I use at work: C++ and Qt
Yes, I'd prefer Rust and Slint/Tauri.
But like a prostitute I don't do what I love, I do what pays the bills.
> Yes, I'd prefer Rust and Slint/Tauri.
Ah, you like masochism I see. I bet you use it for your personal projects, but not at all for commercial projects. It’s just not there yet.
Talking about Slint or Tauri? AFAICT they aren't complements but alternatives.
I think it's a little too niche, and as embedded processors get more and more powerful, we'll just see the same trend of doing all UI in a browser instead
I do like working in it, though!
You don't need powerful microprocessor for UI. Just some sort of connection. WiFi, network, file system. Then UI can run in browser on tablet, desktop...