this post was submitted on 17 Sep 2023
77 points (97.5% liked)

Programming

17523 readers
489 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

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 [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
77
Roblox Game Devs Duped by Malicious npm Packages (www.cyber-oracle.com)
submitted 1 year ago by [email protected] to c/programming
15 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 21 points 1 year ago (2 children)

At some point, npm supply chain attacks are going to stop being news and start being "Tuesday."

... JS on the backend was a mistake.

[–] noli 7 points 1 year ago (1 children)

JS was a mistake.

[–] [email protected] 3 points 1 year ago

It wouldn't have been if it kept to the original purpose of some simple tasks and such, but we can't have nice things.

[–] JackbyDev 2 points 1 year ago (1 children)

JS on the backend was a mistake.

Typo squatting is not unique to JS.

[–] [email protected] 2 points 1 year ago

True, but it's uniquely bad in the JS world. Developers tend to rely on libraries in almost cartoonish excess.

  • The language is shit in general, leading to an endless parade of frameworks and packages designed to paper over the sore spots.
  • The lack of a well-rounded One True Standard Library™ means lots of trivial functionality needs to come from somewhere.
  • Micro-dependencies are commonplace, leading to bloated dependency trees. I'd guess this is caused by a combination of both culture and the fact that you often want your JS artifacts to be as lean as possible.