3 ms·

Hahaha, Joel Spolsky predicted exactly that IN THE YEAR 2000: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonso

• kazinator 2y ago
  Times have changed. Code now does acquire bugs just by sitting there. Assholes you depend on are changing language definitions, compiler behavior, and libraries in a massive effort concentrated on breaking your code. :)
  • _lvbh 2y ago
    Golang really is the best when it comes to backwards compatibility. I'm able to import dependencies from 14 years ago and have them work with 0 changes
  • 0xfeba 2y ago
    It acquires bugs, security flaws, and obsolescence from the operating system itself.
  • lpapez 2y ago
    > Assholes you depend on are changing language definitions, compiler behavior, and libraries in a massive effort concentrated on breaking your code. :) Big Open Source is plotting against the working class developer.
    • bobnamob 2y ago
      Or phrased positively, Big Open Source keeping the working class developer employed
  • kerkeslager 2y ago
    In general, when people say this sort of thing, if I dig into what exactly they're doing I discover they're importing half of npm/pypi/etc. My code doesn't acquire bugs by sitting there in 2024 any more than it did in 2004. On most projects these days I'm using Django + Preact + HTM. Preact and HTM get loaded from static files by my root Django template. My PyPi dependencies are pinned to specific versions, and usually I have <10 (usually it's just Django and Django REST framework, sometimes it's even just Django).
• deleted 2y ago
  [deleted]