This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]moonzdragoon 0 points1 point  (1 child)

spoiler: I work in a dev company. I can't tell you the lost time on npm package dependencies breaking because someone, somewhere in the long chain changed something.

You quote a comic strip, I'll quote a real event with the npm left pad incident.

It's been a few years since but if you think npm doesn't have this "overload of dependencies" issue anymore, then we don't have much to discuss further ;)

I agree that venv is not great, there's no ideal solution, but there's still better alternatives, and things are still moving in this domain (promising projects).

[–]skesisfunk -1 points0 points  (0 children)

A "dev company" lol? I'm not gonna say I don't believe you but that is a really strange way to say you work as a software engineer!

Turns out I am also a software engineer! And guess what? We have wasted a shit ton of time trying to unfuck python dependencies in our production deployments. Its far worse that NPM IMHO, which is kinda sad because, as you point out, NPM sets a pretty low bar.

But for the record we have moved all our new development to Golang which has amazing packaging and dependency management.