4 ms·

Yes, but we now live in a world of weaponized package takovers, such as the Kite incident with IDE plugins, or the security mishaps that have afflicted npm. The

Yes, but we now live in a world of weaponized package takovers, such as the Kite incident with IDE plugins, or the security mishaps that have afflicted npm. The “I’m a good guy, you’re a good guy, we’re all good guys” approach doesn’t really cut it any longer.

stephenr 8y ago
I'm unfamiliar with 'the Kite incident' but the NPM incidents have been due to a) the ass-backwards approach the company took to building a package manager. b) the new development paradigm of "fuck it, find a library". Flying Spaghetti monster forbid these hipster developers actually have to write some fucking code themselves, its easier just to duct-tape together 200 different 'libraries', half of which do what you could do in 5 lines or less, and produces a dependency tree like fucking crab grass.
- gronne 8y ago
  A bit ranty but i’l allow it because you are right. All praise his noodleness.
- wlesieutre 8y ago
  For reference on Kite: https://forum.sublimetext.com/t/rfc-default-package-control-channel-and-package-telemetry/30157 https://forum.sublimetext.com/t/rfc-default-package-control-...
- coleifer 8y ago
  Thankfully they mostly stay in their own little excrement filled sandbox.