5 ms·
... Until the first person ports QT or GTK and suddenly WASM is just pushing 60 PNG frames a second into a canvas.
by forgotpw1123 9y ago
... Until the first person ports QT or GTK and suddenly WASM is just pushing 60 PNG frames a second into a canvas.
- tyingq 9y agoIt may get there eventually, but currently, having to pass the JavaScript/wasm chasm for DOM manipulation is really slow. https://github.com/rust-webplatform/rust-webplatform/issues/20 https://github.com/rust-webplatform/rust-webplatform/issues/...
- paulddraper 9y agoBut canvas is faster.
- orange8 9y agoCanvas is part of the DOM. It is a DOM element that JS can draw graphics on.
- abecedarius 9y agoNot a problem: you can ask the canvas for an arraybuffer to draw on, and pass that to the wasm code. I did this with asm.js in place of wasm (which didn't exist yet) in http://wry.me/hacking/Turing-Drawings/ http://wry.me/hacking/Turing-Drawings/ and you can judge the speed yourself. (As that page describes, there was some overhead from calling from JS to asm.js at least when asm.js first came out. I don't know the current figures.)
- orange8 9y agoasm.js is valid Javascript. It is a valid subset of js that the browser js engines understand, even for the older ones like IE 8. JavaScript has direct access to the DOM, with webassembly, not yet. It may in the future, its still in the proposal phrase (https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md https://github.com/WebAssembly/gc/blob/master/proposals/gc/O...) So the way to do it today would be WebAssembly -> asm.js/js -> canvas
- abecedarius 9y agoGood point about the proposal -- that'll be the answer in the end. asmj.js as JS is irrelevant to the point I was making, because if you access the DOM directly, your code won't verify as the asm.js subset, and so won't run via the asm.js engine.
- orange8 9y agoThe asm.js engine is the javascript engine. asm.js is javascript. asm.js === javscript
- abecedarius 9y agoNo: that's a choice that Chrome made and Firefox didn't, for example.
- deleted 9y ago[deleted]
- aeleos 9y agohttps://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death... Your comment immediately made me think of this. Highly recommended talk for anyone that hasn't seen it. It goes through a "fictional" (maybe not so much anymore) history of javascript until 2035. We are getting pretty close to javascript all the way down.
- pjmlp 9y agoI am betting WASM will be the revenge of plugins. And then, just like the ad spams using JS, its advocates will be getting more than they asked for. Get ready for WASM blockers.
- flukus 9y agoBut management won't pay to redevelop the whole site, so they'll just embed the content in a QtWebKit widget. We can still block ads at the network level.
- pjmlp 9y agoSure they will. Instead of "why I moved from Angular/React/.... to Vue.js", it will be "why I ported into WASM".
- slackingoff2017 9y agoWASM is going to kill spidering. We can't leave HTML if we want google to be able to read the page. I think Google is very afraid of this. Hence their push for Angular/Polymer/AMP. If they can build a good enough platform in JS they can stall the inevitable. In the future only marketing parts of the site will use JS/HTML. The "web app" part will be some language compiled to WASM throwing frames to the canvas
- smrq 9y agoIn a world where SEO consultants exist, you foresee an inevitable future where Google is killed by a massive wave of companies rewriting their websites to be un-Googleable?
- slackingoff2017 9y agoThe big players are increasingly doing it already. LinkedIn and Facebook only have very limited spidering. What Google has liked to do recently is take all your data and replace your service. Search for recipes, jobs, music, or weather for examples. They're trying to make leaving the homepage irrelevant by using sites data in their search results. Eventually the web will rebel.