News for hackers. Stuff that matters.

A comment on How V8 handles JavaScript properties internally. Parent comment

Re:How V8 handles JavaScript properties internally by pjmlp on Thursday August 31, 2017 @02:18AM (#15138488)
There are already ongoing efforts to port JVM and .NET environments into WASM, although currently it is more of a proof of concept.

When WASM gets mature, expect the return of the plugins, maybe even a Flash to WASM compiler.

[ Parent | on HN ]
Re:How V8 handles JavaScript properties internally by hajile on Thursday August 31, 2017 @08:58AM (#15139916)
I don't believe the answer to JS is downloading, and compiling the entire JVM.
[ Parent | on HN ]
Re:How V8 handles JavaScript properties internally by pjmlp on Thursday August 31, 2017 @09:10AM (#15139984)
As I mentioned, It is already happening.

https://github.com/SteveSanderson/Blazor

https://github.com/kg/ilwasm

https://github.com/konsoletyper/teavm

In two to three years time, Flash will be back.

[ Parent | on HN ]
Re:How V8 handles JavaScript properties internally by sqeaky on Thursday August 31, 2017 @10:55AM (#15140728)
I think you are adding extra steps that are not needed. The programming model requires the JVM there are a few tools that compile Java directly to native code. There are tools that compile it to java script, and there are beta quality tools that compile it to WASM.
[ Parent | on HN ]