If you’re into this JS ecosystem (and given that your reading this post - I think you are) you must / should have heard of something like WebAssemb...
For further actions, you may consider blocking this person and/or reporting abuse
Whilst your stats are correct your assumptions are wrong.
Wasm is slow with strings because the MVP doesn't support strings. Once it does the performance bench marks will change in favour of wasm.
But you are also wrong if you think the death of JavaScript will come as a result of wasms performance.
JavaScript is the new cobol because developers want to program in a single language. As soon as wasm supports a wide variety of languages the long slow death of JavaScript will begin.
JavaScript is more like the new Visual Basic For Applications, you have to use it because is the only option.
When other options appear, some developers will stay with js, some others will innovate applying more robust technology to the web.
Nothing that have not happenned before.
I don't think that is the case. Currently a lot of people enjoy writing JavaScript, which wasn't always the case.
Of course people enjoy it, they actually enjoy it too much.
Well we start to use dart maybe
You miss the plot. Wasm isn't just about super fast division by zero its about introducing actual programming languages to web development and offer an exit to that dreaded bloat of inconsistency called js. If this takes a performance hit, me personally can't care less...
Indeed you're right. But (at least for me) WASM is advertised as new format for better speed and efficiency. I think that support for LLVM-compiled languages is just a side-effect. If course, I can be wrong but it's my opinion.
While everything you said, I think it comes as a disappointment to many. WASM was hyped up to be (wrongly in hindsight) to be the way the JavaScript monopoly was going to be (finally) toppled. I love JS. But I am by no means the only developer, and we also shouldn't expect one language to be able to do everything. I thought WASM binaries were going to (in a way) almost be like bringing
.jars back to the Web, but interoperable with the JS Module system. As you have discussed in the article, this is not the case. WASM is meant to simply offload intensive math heavy operations to a lower level format.It's going to be for both, it's just that they are not there yet, it's a mvp after all.
If you want to see what's coming, check this article by Lin Clark hacks.mozilla.org/2018/10/webassem...
No matter how proficient I am in JS, I still wish it would disappear :)
WASM is a miracle, my only fear regarding it is that the order of new features will be Garbage Collection Primitives then Threads then DOM access, which means that languages familiar to serverside frontend developers like Ruby and Python will flood the scene.
I hope it will be DOM access then Threads (all before Garbage Collection Primitives), so that Rust UIs have time to create a great ecosystem.