News for hackers. Stuff that matters.
Re:Experimental support for WebAssembly in V8 by s3th on Tuesday March 15, 2016 @11:12AM (#11290208)
WebAssembly doesn't intend to replace jQuery, D8, or CSS. However, we definitely plan to enable efficient DOM access. Doing so requires supporting some sort of native Garbage Collection, as well as the concept of opaque reference types. See more here: https://github.com/WebAssembly/design/blob/master/GC.md
Re:Experimental support for WebAssembly in V8 by tadlan on Tuesday March 15, 2016 @11:17AM (#11290260)
Any specific plans for python support?
Re:Experimental support for WebAssembly in V8 by jfbastien on Tuesday March 15, 2016 @11:44AM (#11290462)
Python is just another language VM. C Python should work just fine in WebAssembly, and bridging the APIs to the web (e.g. filesystem, etc) is already possible through Emscripten.

We don't plan to do things for WebAssembly, we plan to make WebAssembly powerful enough that anyone can run their language VM :-)

Re:Experimental support for WebAssembly in V8 by esailija on Tuesday March 15, 2016 @04:05PM (#11292560)
I think what they meant is that they could use python without having to also ship the implementation like CPython. I mean, that thing is huge. How is it feasible to serve 10mb for a website?
Re:Experimental support for WebAssembly in V8 by tanlermin on Tuesday March 15, 2016 @04:20PM (#11292660)
Yes, thats what I meant.
Re:Experimental support for WebAssembly in V8 by BuckRogers on Tuesday March 15, 2016 @02:30PM (#11291884)
That's awesome and means alongside ObjectiveC, I effectively waited out deep diving on 2 (soon to be) formerly popular programming languages. I get to use my preferred language, Python, for even more.
Re:Experimental support for WebAssembly in V8 by tadlan on Tuesday March 15, 2016 @12:02PM (#11290604)
Gotcha!