Programming

17303 readers

57 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

145

Why is the Node ecosystem so demanding? (sh.itjust.works)

submitted 1 year ago by planish@sh.itjust.works to c/programming@programming.dev

55 comments fedilink hide all child comments

Steps to reproduce:

Start a Node project that uses at least five direct dependencies.
Leave it alone for three months.
Come back and try to install it.

Something in the dependency tree will yell at you that it is deprecated or discontinued. That thing will not be one of your direct dependencies.

NPM will tell you that you have at least one security vulnerability. At least one of the vulnerabilities will be impossible to trigger in your particular application. At least one of the vulnerabilities will not be able to be fixed by updating the versions of your dependencies.

(I am sure I exaggerate, but not by much!)

Why is it like this? How many hours per week does this running-to-stay-in-place cost the average Node project? How many hours per week of developer time is the minimum viable Node project actually supposed to have available?

you are viewing a single comment's thread
view the rest of the comments

[–] ono@lemmy.ca 26 points 1 year ago* (last edited 1 year ago) (3 children)

My take: It's because the "trust everything from everybody" model is fundamentally broken.

Note that trust is not only about avoiding malicious or vulnerable code, but also about dependability. Even if you ignore the "supply chain" security problems inherent in this model, it practically guarantees that the breakage you describe will happen eventually.

This is part of why I prefer languages with robust standard libraries, and why I am very picky about dependencies.

[–] lemann@lemmy.one 4 points 1 year ago

I personally don't trust NodeJS libraries that much - I always run projects inside Docker as a regular user with access to the working directory, just in case the supply chain is poisoned.

In the case of Python, particularly when I was testing out the LLaMA model, I just stood up a new VM for that. Back then safetensors wasn't a thing, and the model tensor file format (python pickle-based) could potentially store arbitary code.

Robust standard libraries are amazing to have.

[–] howlongisleft@lemmy.world 3 points 1 year ago (1 children)

Thank god for proxy registries. I love Node, but it's like using a house of cards as the foundation of a skyscraper.

[–] BrianTheeBiscuiteer@lemmy.world 3 points 1 year ago

The fact that NPM can't use multiple registries (yes, I know about scoped registries) is astounding. For every other language my org will separate artifacts into half a dozen or so virtual repos. The artifact team is quite annoyed that Node/JavaScript has to all go into one uber-repo.

[–] odbol@lemmy.world 0 points 1 year ago (1 children)

What languages are those? And if you say C/C++ I'm going to laugh

[–] planish@sh.itjust.works 1 points 1 year ago (1 children)

The C++20 or so STL actually has things in it now.

[–] kono_throwaway_da@sh.itjust.works 3 points 1 year ago (1 children)

It's been better but still has a long way to go though, particularly regarding string handling

[–] Decker108@lemmy.ml 1 points 1 year ago

They still haven't figured out string handling?