Well, this is a spicy take first thing in the morning. The "JavaScript will eat the world" narrative, which I see a lot, is so completely foreign to me; JavaScript is absolutely useless for solving any of the problems I want to solve. https://twitter.com/lapcatsoftware/status/971232940859510784 …
-
This Tweet is unavailable.
-
Replying to @stephentyrone
Same. *imagines doing any kind of performant/precise scientific code in JS* Yeah that's never happening.
1 reply 0 retweets 0 likes -
Replying to @bofh453 @stephentyrone
But doing that kind of scientific code is what Webassembly is for*... * Not an endorsement.
1 reply 0 retweets 0 likes -
e.g. You'd call wasm from JS just like you'd use __asm__ in C or link to code written in assembly.
2 replies 0 retweets 0 likes -
People writing precise scientific code do not want to write wasm. Actually, no one wants to write wasm. Wasm is a back-end. It's adequate but bland.
1 reply 0 retweets 5 likes -
It's also going to take a long time to "get there" in terms of being a viable backend for anything serious. They're in the "hack together stuff to make it look like it's working" stage.
3 replies 0 retweets 2 likes -
I'm pretty sure it's also going to replay all of the mistakes from the early days of C, coupling itself too tightly to one arch's implementation details for short-term convenience/performance, rather than thinking about the right abstractions.
1 reply 0 retweets 2 likes -
One thing that's a mess is that they made wasm functions direct callable to/from js ones, with lots of problems that entails. I don't see how you can call it an "assembly" if you do that...
1 reply 0 retweets 0 likes
They seem not to have, and not to be able to create, a working setjmp/longjmp.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.