[bsnnkv]

I've unfortunately had this experience many times in the Javascript ecosystem as a whole.

I recently started writing about going back to a Rust project (check my submissions if you're interested) after 2 years and the experience couldn't be more different (incredibly positive, can't say enough good things).

I would love to develop more for mobile platforms, but I just don't think the cost to my mental state is worth it. I actually ended up killing two mobile apps for my main solo project and replacing them with iOS shortcuts and a Discord bot which thankfully provide 99% of the same functionality that the apps previously did.

I know it's not possible for every use case, but if your mobile app is primarily used to send API requests with payloads of text/images/videos, you'd be surprised how far you can get just using iOS shortcuts these days.

[fbn79]

Instead I have found working on my 5 years old Javascript projects very easy. Even with this old projects NPM can download the very specific deps without problem thanks to the commited lockfile. Then I can easly install the required node.js version (stated in the package.json) with NVM and no other problem arise.

[Sysctl232]

Maybe this is true when you have an Angular js 1.0 project on Node.js and want to update to Angular 15. But that's not because of Node.js. I manage a ton of older Node.js projects and there is little to no friction.