3 ms·
And yet that hacked together document rendering engine manages to be less painful to use than the the current show of UI toolkits. I think we'll get there even
by Spivak 10y ago
And yet that hacked together document rendering engine manages to be less painful to use than the the current show of UI toolkits.
I think we'll get there eventually but until a native toolkit presents an interface as easy to use as the web developers are going to take the path of least resistance.
- mbel 10y ago> I think we'll get there eventually but until a native toolkit presents an interface as easy to use as the web developers are going to take the path of least resistance. Like Qt did with QML? http://doc.qt.io/qt-5/qml-tutorial1.html http://doc.qt.io/qt-5/qml-tutorial1.html
- ryanpepper 10y agoYeah, but Qt has licensing costs for commercial use...
- uzoodoo 10y agoQt is LGPL, so unless you need to link to it statically or make proprietary modifications to Qt itself, you don't need to pay licensing costs.
- ryanpepper 10y agoAh right, I wasn't aware of that.
- rsynnott 10y agoQt is (largely; a couple of optional components are GPL) LGPLv3, so can be used commercially without getting the commercial license.
- pjmlp 10y agoOh, lets be professionals and not pay for our tools like everyone else does, who needs money anyway!
- zigzigzag 10y agoLess painful according to who? From reading this thread it appears that most devs claiming it's incredibly easy have never actually worked with other UI toolkits at all, so their experience is largely worthless. I've done web UI dev. I've also written code using GTK, Qt, Windows, Swing and JavaFX. A good modern UI toolkit like JavaFX or Qt blows the web stack out of the water on almost every metric. Developer productivity, correctness, speed ... you name it.