4 ms·

exactly, unless he really has something super special, QT should fix all his jokes. I don't use QT, but I think QT rarely has competition as far as cross-platfo

• rapsey 8y ago
  Qt and wxwidgets pretty much force you into using C++ and maybe python. If you have to deal with all that baggage, then you might as well go build the UI layer native.
  • grawprog 8y ago
    Huh? https://wiki.qt.io/Language_Bindings https://wiki.qt.io/Language_Bindings 5.1 Qt for Python (PyQt) 5.2 Qt for Ring (RingQt) 5.3 Qt for Rust (Rust-Qt) 5.4 Qt Quick for Rust (qml-rust) 5.5 Qt Quick for Rust (qmlrs) 5.6 Qt for Crystal (qt5.cr) 5.7 Qt for Go (qt) 5.8 Qt for C#/Mono/.Net (QtSharp) 5.9 Qt for C#/Mono/.Net (Qml.Net) 5.10 Qt for D (QtE5) 5.11 Qt for Haskell (qtHaskell) 5.12 Qtah 5.13 Qt for Julia (QML.jl) 5.14 Qt Quick for Haskell (HsQML) 5.15 Qt Quick for OCaml (lablqml) 5.16 Qt Quick for Node.js (Brig) 5.17 QML bindings for Nelson language
    • krageon 8y ago
      Quoting an article's (no doubt extensive) list of bindings for whatever library isn't a great way to start off a conversation about usable bindings in a given language. Bindings often exist, but they are not often any good.
    • rapsey 8y ago
      Most of these are limited to the point of uselesness.
      • doubleunplussed 8y ago
        I ship nontrivial PyQt apps. PyQt can basically do anything Qt can do. Multiple inheritance of QWidgets can be dicey, but desired results can usually be achieved by defining mixins that don't subclass QWidget. It works brilliantly, far from "the point of uselessness". For me, cross platform GUIs are a solved problem, and I really can't wrap my head around all the noise to the contrary, or the claims that electron is what saved us.
        • rapsey 8y ago
          Yeah that is why I said C++ and python...
          • doubleunplussed 8y ago
            Apologies, didn't see that
        • billfruit 8y ago
          Python QT bindings are poorly documented, much of the documentation is out of date. Also it appears to me, far too much churn.
          • doubleunplussed 8y ago
            I don't use PyQt's documentation (wasn't even aware it really existed), it's such a literal wrapper that you can just use Qt's documentation. And the only churn was a change about five years ago from a less pythonic API (using wrapped Qt types for most things) to a more pythonic one (using Python's native types where it makes sense). And that wasn't even that bad. Other than that it has no more churn than Qt itself does.
      • grawprog 8y ago
        I use the D bindings to qt regularly when I'm not using dlangui for GUI.
      • aerique 8y ago
  • stagger87 8y ago
    What hyperbole! Writing a cross platform app in C++ using native UI libraries instead of something like Qt would be SO much more work!
  • deleted 8y ago
    [deleted]