←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 2 comments | 18 Nov 24 18:24 UTC | HN request time: 0s | source
Show context
mvkel ◴[18 Nov 24 19:03 UTC] No.42175730[source]▶
> time to run it after not touching it for 4 years

> Two hours of my life gone...

Two hours of work after 4 years sounds ... perfectly acceptable?

And it would have run perfectly right away if the node version was specified, so a good learning, too

This feels like making a mountain out of a mole hill

replies(21): >>42175799 #>>42175818 #>>42175826 #>>42175846 #>>42176217 #>>42176305 #>>42176788 #>>42176958 #>>42181497 #>>42182299 #>>42182564 #>>42182778 #>>42183020 #>>42183093 #>>42183501 #>>42183725 #>>42184814 #>>42192770 #>>42193606 #>>42194518 #>>42211558 #
korkybuchek ◴[18 Nov 24 19:12 UTC] No.42175818[source]▶
> Two hours of work after 4 years sounds ... perfectly acceptable?

Does it, though? Node wasn't exactly new 4 years ago, and plenty of other languages would offer a better experience for even older code -- Java, C, C++ to name a few.

replies(2): >>42180614 #>>42183420 #
1. mvkel ◴[19 Nov 24 06:42 UTC] No.42180614[source]▶
Define "better experience."

1.5 hours to get running again?

1?

In exchange for needing to run C? How many hours would it take to build a Node app equivalent in C, I wonder.

replies(1): >>42181275 #
2. regularfry ◴[19 Nov 24 08:49 UTC] No.42181275[source]▶
0 would be fine. I'd take 0. This could all have been avoided if the interpreter version had been recorded by default somewhere. That's all this needed.