5 ms·
> Can't we just make a proper, easy to use portable desktop application framework please? Qt ticks all your marks (though the "easy" part is through QML which
by jcelerier 9y ago
> Can't we just make a proper, easy to use portable desktop application framework please?
Qt ticks all your marks (though the "easy" part is through QML which is a superset of JS), + mobile, (+ one day web maybe https://msorvig.github.io/qt-webassembly-examples/window_opengl/window_opengl.html https://msorvig.github.io/qt-webassembly-examples/window_ope... though that's fairly experimental).
- IshKebab 9y agoYeah unfortunately it fails at the "10 MB" bit. Hello world in QML is like 50 MB. Also you can't statically link the GPL version which is just a bit of a pain. I agree if it allowed static linking and wasn't huge it would be perfect. Even so there aren't any better alternatives, but it sucks you can't make something as small and portable as e.g. putty.exe, or depends.exe.
- jcelerier 9y agoQt is under LGPL which allows static linking: https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDyn... This way, you can get under 20 megabytes: https://youtu.be/mbs3-XE0HNE?t=1180 https://youtu.be/mbs3-XE0HNE?t=1180 Sadly I don't think it's possible to have at the same time "portable" (including to platforms without UIs at all, like DirectFB on linux) and small. Putty and depends.exe aren't portable at all.
- rlp 9y agoLGPL does not allow static linking. From Qt's legal page: In case of dynamic linking, it is possible, but not mandatory, to keep application source code proprietary as long as it is “work that uses the library” – typically achieved via dynamic linking of the library. In case of static linking of the library, the application itself may no longer be “work that uses the library” and thus become subject to LGPL. It is recommended to either link dynamically, or provide the application source code to the user under LGPL.
- jcelerier 9y agoPlease read the link I posted, which comes from the people who created the LGPL license: > If you statically link against an LGPL'd library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application The only thing that matters from the point of view of the LGPL is that your users are able to update the LGPL parts in your app. This is possible with static linking. Else for instance how would LGPL be possible with languages that don't even have a notion of linking (eg script languages), or which only allow static linking ? See also : https://stackoverflow.com/a/15322678/1495627 https://stackoverflow.com/a/15322678/1495627
- IshKebab 9y agoThat's quite an ambiguous area of the LGPL. Qt is a C++ app so linking it with the `.o` files from your app is going to be extremely difficult. I'm not sure it would qualify for the LGPL and anyone who says it is is frankly just guessing. The language is not clear and it has never been tested in court (and probably won't ever be). I certainly wouldn't base a business on that risky interpretation, and the one business that I have been in that used the LGPL version of Qt dynamically linked it. It's just less risky (plus you don't need to build it yourself then).
- jlebrech 9y agoyep, qt + wasm is the future
- roryisok 9y agoAm I missing something? Doesn't wasm still need a browser to run? What advantage are qt bindings if you still have to load webkit?
- jlebrech 9y agothen when people use the browser they get the same experience as native, not the other way round where people expect a native app and are given a browser masquerading as an app.
- roryisok 9y agoBut if you use qt you're already cross platform and native. Why force the user to fire up a webkit instance to parse your JavaScript when you could code in python or java?
- jlebrech 9y agowe need a compiled language that splits the generated code into backend, UI and a WASM binary.
- j_s 9y agoA cross-platform UI toolkit with a stable history of commercially support seems to be the most reliable foundation to build on, for sure!