Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Fighting the problems of Qt bindings, Qt, Qt's build system to me is just not worth it.

If someone is a Qt and C++ expert, then maybe, but it still seems like an uphill battle compared to web stuff, which to me seems better supported on all platforms.



If you can use webstuff, clearly it wasn't a problem that involved c++ or rust in any way.


... why?

Using a cross-platform backend + UI stack seems like a best of both worlds. ~5 years ago we developed a kiosk for car washes (you could buy a membership online, then use the QR code, but it had also devices to accept coins and banknotes), backend was Rust, frontend was Angular (the kiosk ran Firefox kiosk on a touch screen, and there was even a tablet at the counter that ran an app that was a bundled webview basically).

It worked well on different devices in different sizes, updates were as simple as "yes restart the thing".

Interestingly we had a C++ project shortly before that (number crunching for music recognition, so not really something that you'd do without a high performance language). We picked Rust for the next one because it seemed easier to implement the state machine required to manage the connected devices & clients in it than in Python.

I absolutely don't miss C++ or Qt (or PyQt, or MOS files, CMakeLists.txt shudder)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: