3 ms·

https://www.areweguiyet.com/ https://www.areweguiyet.com/ Until rust catches up with some meaningful feature set that Qt provides starting a GUI project in rus

by heeen2 4y ago

https://www.areweguiyet.com/ https://www.areweguiyet.com/ Until rust catches up with some meaningful feature set that Qt provides starting a GUI project in rust is probably going to be painful.

pas 4y ago
Most GUI apps don't need what Qt provides though. They mostly need stability and cross-platform support, so ... they should start with something like Tauri or Sciter, and if there is something they need natively they will be in a much better situation to pick their poison. https://github.com/tauri-apps/tauri https://github.com/tauri-apps/tauri uses OS provided WebView https://github.com/sciter-sdk/rust-sciter https://github.com/sciter-sdk/rust-sciter uses Sciter
- LtWorf 4y ago
  > They mostly need stability and cross-platform support But Qt provides that… tauri has exactly 1 release, that was done 4 days ago. sciter has done no release in over a year, and has 6 releases total. It would be completely insane to pick either of those instead of Qt.
  - pas 4y ago
    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.
    - LtWorf 4y ago
      If you can use webstuff, clearly it wasn't a problem that involved c++ or rust in any way.
      - pas 4y ago
        ... 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)

by heeen2 4y ago

https://www.areweguiyet.com/ https://www.areweguiyet.com/ Until rust catches up with some meaningful feature set that Qt provides starting a GUI project in rust is probably going to be painful.

pas 4y ago

Most GUI apps don't need what Qt provides though. They mostly need stability and cross-platform support, so ... they should start with something like Tauri or Sciter, and if there is something they need natively they will be in a much better situation to pick their poison. https://github.com/tauri-apps/tauri https://github.com/tauri-apps/tauri uses OS provided WebView https://github.com/sciter-sdk/rust-sciter https://github.com/sciter-sdk/rust-sciter uses Sciter

LtWorf 4y ago
> They mostly need stability and cross-platform support But Qt provides that… tauri has exactly 1 release, that was done 4 days ago. sciter has done no release in over a year, and has 6 releases total. It would be completely insane to pick either of those instead of Qt.
- pas 4y ago
  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.
  - LtWorf 4y ago
    If you can use webstuff, clearly it wasn't a problem that involved c++ or rust in any way.
    - pas 4y ago
      ... 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)