Re:WebAssembly Interface Types: Interoperate with All the Th...
by wahern on Wednesday August 21, 2019 @06:09PM
(#20762408)
WASM is tied to existing JavaScript engines and their constraints. For example, WASM doesn't support more efficient control flow because of the design of V8 (and possibly SpiderMonkey):
http://troubles.md/posts/why-do-we-need-the-relooper-algorit...
Re:WebAssembly Interface Types: Interoperate with All the Th...
by bcheung on Wednesday August 21, 2019 @07:40PM
(#20763135)
Tied to the engine is orthogonal to tied to the language. You can compile C, C++, and Rust to WebAssembly. But you still can't compile JS to WebAssembly.
Given the large amount of code in JS and the number of JS developers, not being able to support a major general purpose language rules out WASM as a cross platform target in my book.
Re:WebAssembly Interface Types: Interoperate with All the Th...
by sroussey on Wednesday August 21, 2019 @08:06PM
(#20763301)
You can compile a subset. See AssemblyScript. Actually more like a subset of TypeScript.
Re:WebAssembly Interface Types: Interoperate with All the Th...
by sideeffffect on Sunday August 25, 2019 @07:20PM
(#20796291)
> statement that the CLR ties you to C# is not justified
it is. F# developers are stuck with the language progress and can't (or don't want to) add big and important features like Type Classes or Higher-kinded Types, until C# adds them first
I think the statement that the CLR ties you to C# is not justified. Can you elaborate why you think this is the case?
Also, WASM is not tied to JavaScript. You can't even compile JavaScript to WASM because it doesn't support the necessary primitives. In fact other languages that are completely different than JavaScript compile to WASM much easier.