←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: 0s | 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 #
mst ◴[19 Nov 24 09:18 UTC] No.42181425[source]▶
I think it was 'A Deepness In The Sky' that posited so many layers of legacy underlying the starship control systems of the era that one of the most crucial positions on a ship was that of 'Programmer-Archeologist.'
replies(2): >>42186821 #>>42194165 #
1. wpm ◴[19 Nov 24 18:49 UTC] No.42186821[source]▶
That sounds great. Added to my list.

I adore the idea of somewhere on the Star Trek Enterprise, underneath the isolinear chips, the EPS conduits, the warp containment field control mechanisms, somewhere, if you dig far enough, override enough, you can get an LCARS screen that is all black, with a small `$` in the upper left and a blinking text cursor, waiting for a command.