FRESH

Hacker News

Home

The Birth and Death of JavaScript (2014)

170 points by subset

by DavidPiper

1 subcomments

I love(?) that he absolutely predicted a global disaster between 2020-2025, he just got the wrong type. Which is very JavaScript.

by eranation

4 subcomments

Surprised no one mentioned this is the guy who brought us this masterpiece. If you haven’t seen it, drop everything and watch it, best 5 minutes of your day guaranteed.
https://www.destroyallsoftware.com/talks/wat

by jdw64

12 subcomments

JS became a compilation target (and it really did), and back then in the video it was asm.js (that's been deprecated, hasn't it?), but then WebAssembly came along... Seeing it actually being implemented and running natively, it seems his prediction was accurate. I mainly use TypeScript myself, and now with Electron, web technologies are wrapped into desktop apps, so web syntax has even entered computer programs. People say Electron is heavy and not great, but it's also the fastest way to support Mac, Windows, and Linux all at once. Sometimes insights like that are surprising.
The 'death' being discussed here means that JavaScript becomes the substrate, a state where you don't use it directly, but it's everywhere. And that has truly come to pass.

by satvikpendem

2 subcomments

The problem is Wasm is not improving nearly as fast as predicted here. We don't have DOM manipulation so we will still need JS regardless as glue code, or just eschew HTML and CSS altogether and render everything on a canvas as Flutter and some Rust GUIs do but that's a shame to lose the feature set of the web.

by oakinnagbe

2 subcomments

Every few years, we invent a better JavaScript. Then we transpile it to JavaScript.

by ksec

2 subcomments

Almost everything happened according to the script. Now we are just waiting for another OS fully based on browser technology or WASM OS.
webOS and Firefox OS was at least 20 years ahead of its time.

by RIshabh235

2 subcomments

We’re past the halfway point of Bernhardt’s 2035 timeline; JavaScript hasn’t died yet, but it’s clearly writing its own eulogy in WebAssembly.

by marking-time

0 subcomment

"YavaScript" made me smile.

by j16sdiz

0 subcomment

I skim though it and saw they had something javascript asm.js in kernel.

by checkthisgot

0 subcomment

I think JS, is yet to rise the agents, and using all the next.js components.

by Surac

6 subcomments

My first contact with js was trying to make a button change its color on mouseover. There was no css back then. I bought a book and was so put off from the syntax that i never looked back to js from that day on. Never regretted my decision

0 subcomment

by arkadiytehgraet

1 subcomments

Regardless of the content, this is one of my most favourite talks ever, especially in the delivery aspect. It served me as an inspiration for quite some time when I had to present anything to a wide audience.

by jhatemyjob

0 subcomment

Great talk. I'm glad he was wrong about this. Having js/wasm be the standard ABI would have been horrible. Obviously he could have never predicted in 2014 that Valve would pour a metric fuckton of resources into improving Wine/Proton, to the point of getting x64 binaries to run on other architectures. But here we are, past the year of the Linux desktop, well on our way to the year of the Linux handset.

by roshiya

0 subcomment

[dead]

by naveen99

1 subcomments

interpreted languages carry a lot more context than compiled ones. Sandboxed compiled languages don’t have the context baggage, but come with other parts of the brain dead.