51–60 of 346 posts
Earlier quoted context omitted.
Couldn't the compiler take care of optimizing those when necessary? After all I don't know of any "real" assembly with tail call support...
Most assembly languages have a "jump" instruction, though -- wasm supports only structured control flow.
Earlier quoted context omitted.
Until wasm supports proper tail calls, only the ones with uninteresting control structures.
Tails calls can be easily replaceable by br or loop instructions, nothing special for anyone with compiler design knowledge.
There's an expressiveness gap between languages with and without proper tail calls. (Unless you're willing to accept the unsafe-for-space solution.)
Earlier quoted context omitted.
I don’t think there is a single web site with human readable javascript on the web anymore. With all the bundlers and minifiers manglers etc, delivered js is already as closed as a wasm binary would be.
> I don’t think there is a single web site with human readable javascript on the web anymore. Meaningless hyperbole - there are plenty. You're posting on one right now.
For those in the know, what doors is web assembly expected to open? Better cross platform platforms via a browser wrap? Will new types of browser applications be possible that aren't now in JS only world? What are they?
Expect every language out there to have a WebAssembly implementation, including Flash.
Earlier quoted context omitted.
Tails calls can be easily replaceable by br or loop instructions, nothing special for anyone with compiler design knowledge.
That's true as far as it goes - but wasm lacks general "goto" instructions (across procedures), and loops only work for self-tail-calls. There's an expressiveness gap between languages with and without proper tail calls. (Unless you're willing to accept the unsafe-for-space solution.)
How far I would get before losing interest or facing those issues, I don't know.
Java applets 2.0, we are back to square one, yet again. People don't learn. The web dev community have just managed to force browsermakers to unify web development on browser side JS, and throw Java applets, activex, and action script to the bucket, just to have a kind of JVM being made a part of the web standard, and forced upon us yet again.
Do you? The comparison with Java has been made before, including on HN.
"While Java and Flash [2] came early to the Web and offered managed runtime plugins, neither supported highperformance low-level code, and today usage is declining due to security and performance issues. We discuss the differences between the JVM and WebAssembly in Section 8. "
https://github.com/WebAssembly/spec/blob/master/papers/pldi2...
Earlier quoted context omitted.
Expect every language out there to have a WebAssembly implementation, including Flash.
Is there really demand for the resurgence of Flash? In its final years it was used to provide capabilities that the browser couldn't, like video playback. Web Assembly will not provide that same advantage.