#dependencies

Those arguments don't really hold water at all. Games are more than just the sum of their parts. Making all of the pieces work together cohesively is a huge amount of work. Every game is a complex web of features and content. Any given feature is dependent on a bevy of other systems and features and any failures can easily cascade into catastrophe. One of my acquaintances works on the Call of Duty franchise - she told me that they often have difficulty porting features between the single and multiplayer versions of the game due to the way the technology is set up. It can take days of engineering and scripting to bring a feature from DMZ to regular multiplayer or another game mode.

[Join us on Discord] and/or [Support us on Patreon]

Got a burning question you want answered?

Short questions: Ask a Game Dev on Twitter

Long questions: Ask a Game Dev on Tumblr

I think I mean something more like what happened with leftpad is in the broad class of threats where reasonable professional diligence is good protection, and what happened with node-ipc is not. There are a few aspects to this:

1) You’re only in the position to be really hurt by the leftpad rug-pull if you’re the kind of person who should be practicing professional diligence, ie, a professional. If you’re just a kid trying to learn programming, it’s annoying (and confusing) if you can’t download your dependencies for a while, but nobody is relying on you. Whereas that same kid could suffer painful data loss from node-ipc.

2) While pulling leftpad was bad, if you’re in a position where you could be hurt by leftpad and don’t have procedures in place that deal with issues like leftpad, you’re in the position to get hurt by random, non-malicious errors.

You asked, so here they are: all the European states in the style of Marshall Islands + some edits & five dependencies so there's no weird blank space

Dependencies and packages and libraries galore