" Codebases from years ago are still rock-solid." This is the biggest thing for me. I recently pulled down an 8 year old hobby Java/Maven project I had and it compiled and ran perfectly on the first try. Imagine trying to get an 8 year old javascript project to work...

▲

port11 4 days ago | parent | next [-]

At my previous startup (co-founder who made all technical decisions) we were unfortunately stuck with React Native. I had Mondays that started with the project not building after some dependency changes. Imagine something failing to build 3 days after you've last touched the codebase…

▲

c-hendricks 5 days ago | parent | prev | next [-]

Just did, I installed the version of node specified somewhere, codified it into mise, and was up and running in no time.

▲

5 days ago | parent | prev | next [-]

[deleted]

▲

elbrian 5 days ago | parent | prev | next [-]

You mean like this?

nvm use && npm i && npm run dev

▲

Aeolun 5 days ago | parent | next [-]

Does NPM work for you in the first place? Much less after 5 years? They’ll have gone through 2 major revisions on their lock file format, and it’ll complain you don’t have the exact version of node specified in your package.json

▲

parasti 5 days ago | parent | prev | next [-]

Oops, one of the dependencies is a C++ library that doesn't compile on your less-than-five-years old arch.

▲

vrighter 5 days ago | parent | prev | next [-]

That only works if the project is constantly maintained. Otherwise it can and will break in time.

▲

chipsrafferty 5 days ago | parent | prev [-]

Ok, 50 packages have critical vulnerabilities now

	▲	techpression 4 days ago \| parent [-]
		And another 30 didn't use versioning correctly so they installed new dependencies of their own that broke things three levels deep. Yes, based on a true story.

▲

fatata123 5 days ago | parent | prev [-]

[dead]