4 ms·

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-of-java

by futune 5mo ago

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-of-javascript 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.)

phoe-krk 5mo ago
Just substitute asm.js with WASM and you're still on the right track.
muvlon 5mo ago
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.
- mikece 5mo ago
  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.
  - DarkUranium 5mo ago
    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.
    - nextaccountic 5mo ago
      Can you talk more? I've seen people say only good things about wasm
      - avadodin 5mo ago
        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.
        nextaccountic 4mo ago
        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
- tadfisher 5mo ago
  Yagrum Bagarn has something for you.
bvisness 5mo ago
Don't worry, YavaScript will live forever.
- mikece 5mo ago
  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..."
- egeozcan 5mo ago
  In Germany, it's still not uncommon to hear Yava and YavaScript.
  - dagurp 5mo ago
    It's the only pronunciation you'll hear in Iceland
  - bonesss 5mo ago
    I understand that Jawohl is still quite popular there, but JawohlScript adoption is sadly lagging.
  - deleted 5mo ago
    [deleted]
mikece 5mo ago
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).
ksec 5mo ago
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.

by futune 5mo ago

phoe-krk 5mo ago

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

muvlon 5mo ago

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.

mikece 5mo ago
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.
- DarkUranium 5mo ago
  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.
  - nextaccountic 5mo ago
    Can you talk more? I've seen people say only good things about wasm
    - avadodin 5mo ago
      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.
      - nextaccountic 4mo ago
        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
tadfisher 5mo ago
Yagrum Bagarn has something for you.

bvisness 5mo ago

Don't worry, YavaScript will live forever.

mikece 5mo ago
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..."
egeozcan 5mo ago
In Germany, it's still not uncommon to hear Yava and YavaScript.
- dagurp 5mo ago
  It's the only pronunciation you'll hear in Iceland
- bonesss 5mo ago
  I understand that Jawohl is still quite popular there, but JawohlScript adoption is sadly lagging.
- deleted 5mo ago
  [deleted]

mikece 5mo ago

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).

ksec 5mo ago

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.