Re:Qt for WebAssembly
by pier25 on Tuesday June 19, 2018 @03:58PM
(#17349838)
If anyone is curious, everything is being rendered on canvas.
[ Parent
| on HN ]
I think the plan would be to eventually render a QML based interface on a webgl canvas, which in theory would have a better performance than a DOM based interface.
I'm not an expert but maybe a case can be made that a lightweight rendering engine on WebAssembly can be faster than C++ DOM rendering engine which needs to support lots of legacy stuff.
There's also https://qmlweb.github.io/, which renders QML into a DOM tree. Which will probably never be a full-featured an implementation as QML as one painting onto canvas, but is a lot more web-native.
Initial prototype aside, I wonder how married the Qt team is to the canvas approach.
Improved performance is great, but not very helpful if it means the solution gets considered a nonstarter by almost everyone evaluating it. As long as the responsiveness is acceptable, I'd rather have a DOM-based approach that supports accessibility and generally behaves like other web pages; users who need better performance can always switch to the native app.
Maybe some kind of hypothetical hybrid approach could somehow get the best of both worlds, or maybe both render targets could be supported (with DOM default/preferred and canvas recommended for use cases like games that need the performance gain).
What are the implications?
After 5 seconds of looking at it, I'm noticing that my scroll wheel doesn't work and that typing in Hebrew results in Unicode boxes. Meaning, it is acting different enough from my browser that I'm noticing it.
Re:Qt for WebAssembly
by 0x4f3759df on Tuesday June 19, 2018 @04:52PM
(#17350214)
Somebody is going use a technology similar to this to defeat ad-blockers.
damm you, cold hard truth!
but it is really cool
Re:Qt for WebAssembly
by 0x4f3759df on Tuesday June 19, 2018 @09:30PM
(#17351719)
People argue that we will just block ads at the transport level, but I don't see why the site won't just add an extra hop and serve the ads from their server.
> serve the ads from their server.
because ad networks don't trust their own clients to not spoof the traffic numbers.
On the bright side, punch the monkey in 3d/vr could be cool.