News for hackers. Stuff that matters.

A comment on The tragedy of running an old Node project. Parent comment

Re:The tragedy of running an old Node project by blenderob on Tuesday November 19, 2024 @07:40AM (#42182778)
> Two hours of work after 4 years sounds ... perfectly acceptable?

Pefectly acceptable? Perfectly? Really? I have 10 year old C and Go projects that build and run fine as if nothing has changed. I can upgrade the dependencies if I want to but that's on me. The projects themselves have no problem building and running fine.

[ Parent | on HN ]
Re:The tragedy of running an old Node project by danieldk on Tuesday November 19, 2024 @02:48PM (#42187366)
Just to try it out, I took one of my old C projects written in 2010, last code update in 2012. It's a machine learning utility to train maximum entropy rankers. I was a bit worried because it used CMake (rather than a vanilla Makefile). It configured and built without any issues (and super-fast).
[ Parent | on HN ]
Re:The tragedy of running an old Node project by fennecfoxy on Wednesday November 20, 2024 @06:07AM (#42192755)
How many external dependencies/libraries does it use? Ie remote dependencies not stored on your machine?

How complex is the project? I know ML utilities like that can be as simple as 50-100 lines.

[ Parent | on HN ]
Re:The tragedy of running an old Node project by paulddraper on Thursday November 21, 2024 @08:04PM (#42210265)
Lol, Go was notorious for breaking with its "pull from main"/lack of lockfile approach.
[ Parent | on HN ]