|
|
|
|
|
by oaw-bct-ar-bamf
1554 days ago
|
|
Or how about this.
Don‘t use code that some stranger puts on the internet for critical stuff. critical stuff has to be defined per application. For controlling aircraft engines or car engines I for sure as hell do not accept unreliable packages. That’s why contracts exist that hold software suppliers LIABLE for faulty software. |
|
At the moment, supply chain attacks seem to be mainstream enough that a normally trustworthy person could consider doing them, so trust becomes harder.
This is why you don't accept or encourage antifragile/vigilante/cowboy/etc behaviour, or any kind of sabotage of infrastructure.... now it's cool and trendy. There's millions of wannabe unabombers who just need any excuse to disrupt tech.
Remember that guy who wanted people to suddenly pull npm packages without warning?
Tech culture used to be way more awesome. Now it's a bunch of people who wish they were doing pure mathematics or random weekend tinkering, who hate their industry, and would be perfectly happy to see a lot of it gone, and a forced return to the days of paper notes and brass keys with no tracker.