News for hackers. Stuff that matters.
Re:Experimental support for WebAssembly in V8 by jensvdh on Tuesday March 15, 2016 @02:22PM (#11291827)
Because DOM manipulation in C++ sounds like a nightmare to me.
Re:Experimental support for WebAssembly in V8 by geon on Tuesday March 15, 2016 @03:49PM (#11292455)
If you want it to be fast, you probably shouldn't touch the dom.
Re:Experimental support for WebAssembly in V8 by rspeer on Tuesday March 15, 2016 @04:31PM (#11292733)
To the contrary, I think everyone should touch the DOM when they need the DOM. If this is going to be a platform for more than ads and shitty games, it will need to be able to use the browser's exquisitely engineered ability to do text rendering and layout.

Just like Flash or the JS game platforms that are stupid hacks on top of the canvas element, if people have to implement text rendering without the DOM, it'll encourage putting poorly-rendered text in unusable layouts with squirrely scrollbars. We can do better.

Re:Experimental support for WebAssembly in V8 by geon on Tuesday March 15, 2016 @05:06PM (#11292998)
I mean you would do it the react way and only manipulate an abstract representation of the dom.
Re:Experimental support for WebAssembly in V8 by twistedpair on Tuesday March 15, 2016 @04:15PM (#11292630)
C++ speed in the browser... just be sure not to touch the browser.
Re:Experimental support for WebAssembly in V8 by omarforgotpwd on Tuesday March 15, 2016 @02:39PM (#11291958)
I was thinking more about Ruby, Python, or go