Hacker News Reader

Comment by futune | Hacker News Reader

So the death of asm.js is upon us? We are drifting away from the timeline of the prophecy:

https://www.destroyallsoftware.com/talks/the-birth-and-death...

(And to those who haven't encountered this before, I strongly recommend a watch. It may be the greatest tech talk of all time, for certain values of greatest.)

View on HN

With this technology's death, the thread of prophecy is severed. Restore a saved game to restore the weave of fate, or persist in the doomed world you have created.

Yagrum Bagarn has something for you.

Not really: ASM.js became WASM. What killed the possibility of WASM being The One Way to run everything is AI... the one wildcard that Gard Bernhardt didn't predict.

To be honest, with how bad a target WASM is for any existing compiler, I feel like what killed that possibility was WASM itself.

Its IR design is horrendeous.

Can you talk more? I've seen people say only good things about wasm

Not op, but I only know it as the 32-bit single-threaded binary replacement for JavaScript that can't interact with anything naturally yet people get all excited about when they manage to turn their LLVM slop output into it.

Maybe we've been reading different HN submissions.

That was only the MVP.

Wasm nowadays is 64 bits (except for Safari, the IE6 of our time) and has threads.

True about the wasm inability to call JS APIs with no overhead. This sucks

I re-watch that presentation two or three times a year because it's a great example of how to give a presentation, how to structure your slide deck to complement your presentation, and a surprisingly educational tour of the permission rings architecture of operating systems.

And at some point we're going to have a period or war and our psychological attachments to old programming paradigms will be released so that we can move on to a more advanced way of doing things (but that won't stop your bank from running YavaScript for at least another 85 years).

Just substitute asm.js with WASM and you're still on the right track.

Don't worry, YavaScript will live forever.

In Germany, it's still not uncommon to hear Yava and YavaScript.

I understand that Jawohl is still quite popular there, but JawohlScript adoption is sadly lagging.

It's the only pronunciation you'll hear in Iceland

I still refer to it as YavaScript much to the confusion of junior devs. I just tell the new kids: "you had to be there..."

If we substituted war with COVID we aren't that far off as both happened in 2020. We still have to wait till 2035 to see if true.

Reply on news.ycombinator.com