←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 7 comments | 18 Nov 24 18:24 UTC | HN request time: 0s | source | bottom
Show context
uludag ◴[18 Nov 24 18:55 UTC] No.42175643[source]▶
The worst part isn't just that it's nearly impossible to run/update an outdated JS project, but that this process will repeat itself ad infinitum.

On the flip side, anything that uses vanilla JS without a build will most likely run just fine, probably till the end of human civilization.

replies(6): >>42175899 #>>42176382 #>>42177202 #>>42182217 #>>42182764 #>>42189088 #
graypegg ◴[18 Nov 24 19:21 UTC] No.42175899[source]▶
I truly believe some flavour of "Javascript Classic" (some future state of JS before some big shift in syntax/mass migration to something else), C and x86 instructions will follow humanity for the rest of time. There will be javascript somewhere aboard the interstellar spaceships of the future, and we will still complain about it.
replies(6): >>42176310 #>>42176625 #>>42177413 #>>42178137 #>>42179671 #>>42181425 #
peutetre ◴[18 Nov 24 23:05 UTC] No.42178137[source]▶
JavaScript will be killed off by WebAssembly.

Zombie JavaScript will be reduced to being glue code and then not even that.

replies(4): >>42181884 #>>42185231 #>>42188808 #>>42188993 #
1. yen223 ◴[19 Nov 24 10:22 UTC] No.42181884[source]▶
JavaScript will be killed off by webassembly for about 5 years now
replies(1): >>42181901 #
2. peutetre ◴[19 Nov 24 10:25 UTC] No.42181901[source]▶
The difference lately is the number of tools that are now in place for WebAssembly development and the new extensions to WebAssembly (WasmGC, Memory64, etc.).

Despite 28 years of effort at optimization, JavaScript is outperformed by WebAssembly. There's not much coming back from that:

https://jordaneldredge.com/blog/speeding-up-winamps-music-vi...

https://www.amazon.science/blog/how-prime-video-updates-its-...

https://web.dev/case-studies/google-sheets-wasmgc

replies(2): >>42184200 #>>42187303 #
3. liontwist ◴[19 Nov 24 15:07 UTC] No.42184200[source]▶
?? JavaScript was outperformed by every language since it was introduced.

It doesn’t matter. What matters is what people put in their web pages.

replies(1): >>42187768 #
4. yoelhacks ◴[19 Nov 24 19:41 UTC] No.42187303[source]▶
Javascript is outperformed by WebAssembly in the sense that it runs faster.

A lot of things that bring a lot of value to a lot of people are still much, much faster to build via the JS / TS ecosystem.

It absolutely makes sense that calculation-heavy workloads will be ported to WASM, but there's a lot more to building an app.

replies(1): >>42187869 #
5. peutetre ◴[19 Nov 24 20:29 UTC] No.42187768{3}[source]▶
But now JavaScript is no longer the privileged language in the browser.

With WebAssembly every language runs in the browser and runs better.

replies(1): >>42187950 #
6. peutetre ◴[19 Nov 24 20:41 UTC] No.42187869{3}[source]▶
> but there's a lot more to building an app.

Like what? Visual UI designers? WebAssembly's got you covered: https://platform.uno/blog/uno-platform-studio-featuring-hot-...

Running Visual Basic in a C# application compiled to WebAssembly? Sure, why not: https://bandysc.github.io/AvaloniaVisualBasic6/

7. liontwist ◴[19 Nov 24 20:51 UTC] No.42187950{4}[source]▶
And what will prove that is adoption. As others have said, that has been “just around the corner” for years.