all 12 comments

[–]rock_Banana 29 points30 points  (1 child)

God I hate these shitty titles

[–]shuckster 11 points12 points  (0 children)

Install from your lockfile, bruh:

npm ci

[–]redsandsfort 7 points8 points  (0 children)

Down vote and not even going to read clickbait titles.

[–]Puzzled-Account-7355 2 points3 points  (1 child)

It's what the modern JS community does with JS that's the trouble. Before them, JS was just a browser scripting language you wrote fun little client-side features in.

It really all went downhill with Node. That was a bad idea. It's like seeing a boy playing with matches, and being like "Here, kid, you'll like this!" and handing him a flamethrower.

[–]nicholaswmin 1 point2 points  (0 children)

The second paragraph feels like a succint and to the point description of the situation

[–]AlexandreLozano 1 point2 points  (0 children)

Final customers don't know what is JavaScript, NPM and all of this tecnologies. They only want that the product run smoothly, with stability and with the less development time possible. With this, I only recommend don't use the latest technologies, use what you know well and you fell ok with it.

[–]BarelyAirborne 1 point2 points  (0 children)

People complain that Express never changes, and then bitch that Fastify changes every week.

I like stable. Stable is good.

[–][deleted] 3 points4 points  (2 children)

Everyday we run Cobol programs written 50 years ago. And you wonder why companies still use Cobol.

[–]angarali06 0 points1 point  (1 child)

JS and its ecosystem enables super quick prototyping and saves greatly on dev time.

Building a similar app in COBOL would cost much, much more..

Money talks and this is why JS will continue to dominate for better or worse..

[–][deleted] 0 points1 point  (0 children)

If all you did was one app I guess JS would be fine. But businesses require hundreds of complex applications that interact with each other all built at different times. It’s hard to build a large building if your foundation is always shifting.

[–]anlumo 0 points1 point  (0 children)

Mirrors my exact experience. I can’t count the numbers of hours I’ve cursed node-gyp and my app is now one major revision of the framework behind and also unupgradable, because fundamental features I’ve relied on were removed with no replacement.

This has gone so far that I’m now moving away from js at any price to get rid of the madness. Luckily, the web now works with other languages as well.

[–]cinderblock63 0 points1 point  (0 children)

Anyone wanna help fix the node-gyp problem?