News for hackers. Stuff that matters.

A comment on JavaScript TC39 implementing hashmark private class fields. Parent comment

Re:JavaScript TC39 implementing hashmark private class fields by just_astounded on Thursday August 03, 2017 @05:46PM (#14924201)
Until wasm has GC, we're not likely to see much in the way of compile-to-web outside of C, C++, or Rust.
[ Parent | on HN ]
Re:JavaScript TC39 implementing hashmark private class fields by pjmlp on Friday August 04, 2017 @01:32AM (#14926545)
There is already a .NET prototype.

https://github.com/SteveSanderson/Blazor

https://www.youtube.com/watch?v=MiLAE6HMr10

WebAssembly without native GC support is no different that targeting a real hardware CPU. One just has to implement it as well.

As soon as WebAssembly reaches a more mature state, expect the resurgence of plugins and this time around we won't be able to disable them.

[ Parent | on HN ]
Re:JavaScript TC39 implementing hashmark private class fields by gulbanana on Friday August 04, 2017 @11:29AM (#14929408)
blazor is not .NET compiled to WASM. blazor uses a .NET runtime called DotNetAnywhere, which is written in C and compiled with emscripten. the actual .NET IL is then interpreted at runtime by DNA.
[ Parent | on HN ]
Re:JavaScript TC39 implementing hashmark private class fields by pjmlp on Friday August 04, 2017 @04:49PM (#14932138)
True, but the fact is that people are already toying with the idea of bring such runtimes back into the browser.

Also if you bother to read the meeting minutes from WebAssembly meetings, developers from .NET team are present in such meetings.

[ Parent | on HN ]
Re:JavaScript TC39 implementing hashmark private class fields by just_astounded on Friday August 04, 2017 @05:30PM (#14932458)
Fancy!
[ Parent | on HN ]