What opinion just makes you look like you aged 30 years

  • Hagarashi8@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Yeah, but there’s by lot more security improvement by having ability to apply fix for severe vulnerability ASAP than weakening from possible incompativilities. Also, i wonder why i never brought it up, shared libs are shared, so you can use them across many programming languages. So, no, static is not the way to replace containers with dynamic linking, but yes, they share some use cases.

    • argv_minus_one@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Yeah, but there’s by lot more security improvement by having ability to apply fix for severe vulnerability ASAP than weakening from possible incompativilities.

      Um, we’re talking about undefined behavior here. That creates potential RCE vulnerabilities—the most severe kind of vulnerability. So no, a botched dynamically-linked library update can easily create a vulnerability worse than the one it’s meant to fix.

      Also, i wonder why i never brought it up, shared libs are shared, so you can use them across many programming languages.

      Shared libraries are shared among processes, not programming languages.

      • Hagarashi8@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Shared libraries are shared among processes, not programming languages.

        You still can use them in any programming language