←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 1 comments | 18 Nov 24 18:24 UTC | HN request time: 0.203s | source
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 #
1. elzbardico ◴[18 Nov 24 20:32 UTC] No.42176625[source]▶
Well, even Fortran is still around us in some lapack code in numpy and in a lot of the stuff behing scipy, so, a lot closer than a lot of people can imagine.

Basically a lot of AI depends on a bunch of absurdly optimized numeric libraries writen in Fortran.

Fortran is well into the way at becoming a centenarian programing language at 74 years of age.