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 …
-
-
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.
-
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...
-
They seem not to have, and not to be able to create, a working setjmp/longjmp.
End of conversation
New conversation -
-
-
I have no idea what they're doing with floating point, but unless they implement softfloat on top of js & rely on jit to optimize that to robust hardfloat, it's going to be a joke for anything scientific, since js float is so misbehaved..
-
Uh, wasm doesn't run on js
-
My understanding is that it can run on js (with a wasm interp js program) or with acceleration by a wasm-aware browser. Is that wrong?
-
The binaryen js interp is not the intended usage; I believe it was originally added when there were no complete implementations.
End of conversation
New conversation -
-
-
Good thing I included the "not an endorsement" CYA clause then :P- I have no idea how far along it is. Just hear everyone talking about it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.