Everytime I open Origin, I hate my profession

I don't hate game dev.
I hate publishers and management.

I don't hate web dev either.
I hate management and npm.

I feel you.

@Root why on Earth would you hate npm? It's the best package manager I've seen

@Froot probably bloat

@Froot can't disagree. All cons aside it is the one package manager that can by default encapsulate a project without fucking with dependencies.

The only other one I can think off is Java maven projects

@purpletoxicrain bloat?
How is what you download related to the package manager? 😀

@AleCx04 @Froot Seriously?
1) NPM kills itself semi-rarely.
2) It silently fails to install arbitrary dependencies.
3) Arbitrary dependencies seemingly change on disk despite me never touching the project.
4) It doesn't store packages flatly so there can be ridiculous numbers of duplicates.
4a) This kills basic file manipulation on windows.
5) The NPM mentality of "reuse, don't rewrite" that changed into "someone else's code is always better"

NPM is buggy and infuriating and encourages dependency hell.

@Froot couldn't agree more

@Root
1-3: never seen that happen to be honest
4: it's very flat last I checked. Old npm used to best them but that's been changed ages ago
4a: lol windows
5: so you downloading a package for trivial stuff is npm's fault?

So what's a better package manager?

@Froot If I use a dependency, I'm using its dependencies as well. If they're guilty of using tiny meaningless packages for everything, I'm inheriting their garbage.

@Root well don't use that package then. It's a free world, c'mon.

@Froot Sometimes I don't have a choice. Look at bloody Electron. It's a messy monster.

@Root fails silently to install a package? When how and wheeere did you get that? It has legit never happened to me. If anything I get detailed messages as to why something was not installed or notions of the other things it needs. I have projects from 2016 that unless I touch them to explicitly change them they never do. If anything the only issue might arise from installing something globally which as a Ruby dev you already know that such shit is a no no. Never have i ever had the multitude of issues that people complain about and I do have node apps in production.

Still working flawlessly and without issue.

@AleCx04 I've had NPM silently fail to install sub-dependencies on four separate projects. The only solution I've found is to add them as top-level dependencies.

On osx, one of those projects breaks every few months. I never touch it, or even cd into its directory, but when I needed to make those rare changes (or now show it off during e.g. interviews), one of the dependencies (often Susy) no longer works. Running `npm i` and `npm update` don't fix it; I need to run `npm update --depth 999` for it to find and fix the broken dependency/ies. It's happened five times now, on that single project?

I'm glad you haven't had these issues because they're absolutely infuriating

@Root you must be doing something very wrong there because I've never had nor heard of these problems either

@Froot Absolutely nothing wrong as far as I can tell, and I've looked into these issues a lot. They're rare, but there doesn't seem to be a means of preventing them either. That screams "bug" to me