Hacker News Reader

I don't see how it can be feasible to use it for implementations of other languages that don't directly map to webassembly like C. You would have to ship a runtime for the other language along with your application code. The runtime will be either huge with long startup time or small but too slow to be feasible.

View on HN

Whichever it is it can't be worse than implementing other languages in Javascript directly or using stuff like GWT and there are plenty of those already (including development for running Perl 6, btw).

Runtime for a few selected implementations should be very well be packaged or installed along with the browser itself. Failing that, it should be cached.

> Runtime for a few selected implementations should be very well be packaged or installed along with the browser itself. Failing that, it should be cached.

Web Assembly isn't related to this. You can standardize on a new language VM that browsers should ship, like was attempted with Dart. What Web Assembly enables is more efficient VM with better interop to Web APIs than currently is possible, but the most prohibitive thing will not change (having to ship multi megabyte VM along with your application code).

Lots of things will change. If it makes sense to do that, then there will be demand for it.

Here's something already https://news.ycombinator.com/item?id=11269736

Reply on news.ycombinator.com