• MangoCats@feddit.it
    link
    fedilink
    English
    arrow-up
    4
    ·
    23 hours ago

    It it is unsafe to code, full stop.

    The things we’re expecting our code to handle, with the lack of formal verification testing we’re expecting our code to ship with, there’s no such thing as safe. It took 50 years to “build the stack” to where we’re at, and we did it fast and cheap. There’s so many bugs hiding in the lasagna it’s amazing it doesn’t eat itself.

    If you re-build your system from first principles, open source silicon with peer review and constant scrutiny, then the BIOS, then the OS, then the application compilers, and the libraries, all open AND reviewed by multiple concerned parties with formal demonstration of correctness all the way up - the entrenched bug filled lasagna stack owners will smother you, they can’t withstand that kind of competition on an open playing field, your project will die of financial starvation, regulation, buyouts and treachery.

    • lordbritishbusiness@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      21 hours ago

      All the shortcut technical debt is coming due, especially now that there’s a tool able to undertake mass analysis with fairly general rules.

      It’s getting bad out there, and it’s not visible on the surface but a tsunami of bug reports and patches has been sweeping the internet and drowning anything unable to swim.

      For anything that sinks underwater, metaphorically, they’re getting grabbed by automated sharks that are now actively on the attack. If you’re not rapidly fixing everything and monitoring everything closely you’re probably being eaten alive without knowing.

      • MangoCats@feddit.it
        link
        fedilink
        English
        arrow-up
        2
        ·
        20 hours ago

        My approach: I don’t expose anything (that can’t handle it) to the internet. So so many things are “out there” that don’t need to be, shouldn’t be…