3 ms·

So, a Qt package manager written in Go :-) Why not C++ ?

• pjmlp 11y ago
  It isn't written by the Qt guys.
• jrbarron 11y ago
  The decision was between Node, Qt, and Go. At the end of the day, we wanted the possibility to share code between the client and server and Go's server side support is much better than Qt's so we decided to implement it in Go. Go is great for command line tools and being able to cross-compile a Windows binary from a Mac is awesome. Go's static binary approach made deployment trivial in comparison to Node so that made it a winner :)
• pritambaral 11y ago
  Qt isn't really C++-only anymore, at least with QML. Notwithstanding the use of JS for QML itself, there exist some bindings to QML in non-JS, non-C++ languages. So I guess there is demand for Qt (or at least some parts of it) in non-C++-worlds.
  • coldtea 11y ago
    >Qt isn't really C++-only anymore, at least with QML. Notwithstanding the use of JS for QML itself, there exist some bindings to QML in non-JS, non-C++ languages. So I guess there is demand for Qt (or at least some parts of it) in non-C++-worlds. All of these worlds would be loading a ton of C++ QT base libs in any case.
  • jordigh 11y ago
    Qt was never C++, since it always had the MOC.