5 ms·
Hopefully we will not need Unity3d to have high-performance C# engines in browser.
by M8 11y ago
Hopefully we will not need Unity3d to have high-performance C# engines in browser.
- sanxiyn 11y agoHow else you will get C# in the browser? C# is high-level, WebAssembly is low-level, something needs to do lowering. Edit: I don't see how future addition of GC to WebAssembly changes anything I wrote above.
- M8 11y agohttps://github.com/WebAssembly/design/blob/master/FutureFeatures.md#gcdom-integration https://github.com/WebAssembly/design/blob/master/FutureFeat...
- wtetzner 11y agoYou write a compiler from C# to WebAssembly. I don't see how C# is different from any other language in that regard.
- sanxiyn 11y agoI think we are in agreement? Unity3d provides C# to JavaScript compiler. I replied to "Hopefully we will not need compiler to have high-performance C# engines in browser", because that does not make sense.
- wlievens 11y agoUnity is much, much more than a compiler. You'd have to drag a lot of stuff with you and deal with a license.
- M8 11y agoUnity3d provides C# to JavaScript compiler Unity3d does too many things (except new versions of C# :P) and ties to itself. There should be a direct C# -> WebAssembly compiler in future.
- sixbrx 11y agoHopefully it's IL -> WebAssembly, not C# -> WebAssembly.