• scrion@lemmy.world
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    5 months ago

    Let’s not forget that Ubuntu 18.04 has reached its end of life stage in what, April 2023? Pretty much everyone has been dropping support for Ubuntu 18.04 by now, even more impactful dev packages like CMake.

  • Treczoks@kbin.social
    link
    fedilink
    arrow-up
    21
    arrow-down
    2
    ·
    5 months ago

    What does the label “18.04” tell you? It tells me that this installation is far out of date. Whoever complains about this drop of support should consider updating to a more current version for a number of reasons, including “This version of the OS is no longer supported” in general.

    • Gamma@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      5 months ago

      The thing that actually caused issues was that you could no longer use the remote ssh tools with servers that were running Ubuntu 18.04 (still has security updates until 2025), rhel 7 (isn’t eol until June), and “Amazon Linux 2” which is supported until 2025

  • Gamma@beehaw.org
    link
    fedilink
    English
    arrow-up
    10
    ·
    5 months ago

    FYI there’s been an update:

    We have discussed this more in the VS Code team and we have decided to allow VS Code to connect to an OS that is not supported by VS Code (no support for glibc >= 2.28) for 12 more months.

    • hemko@lemmy.dbzer0.com
      cake
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      2
      ·
      5 months ago

      Yeah but in this case we’re talking about ancient OS no one should be using anymore

      Also Canonical is far closer to Enterprise money sucking harpies than to the OSS community

      • shartworx@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        Not the point, though. This is classic Microsoft. It’s Lucy with the football telling Charlie Brown she won’t pull the ball away this time. They seduce the devs to their tools or protocols by “cooperating” and “openness” and then they subvert whatever they joined so the devs are stuck in their ecosystem. A lot of them get away, but a lot stay behind or try to make it work. Every time, they trap a bunch. Maybe the way an Eden’s Whale feeds is a better analogy. I’m sure there’s a perfect analogy somewhere. Maybe I just like coming up with analogies.

        • towerful@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          Seems related to glibc, considering they have backtracked a bit to allow VSCode to connect to unsupported OSs with glibc >= 2.2.8

          Might be related to the recent glibc vulnerability disclosure?

  • ceiphas@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    14
    ·
    5 months ago

    This is an example of a Problem, a working package Manager would solve.

    If you install software that’s not out of a repo or If your package manager ist too stupid to resolve dependencies, it’s totally your fault

    If it came from a repo and MS didn’t update the dependencies, they are assholes. But i doubt it in this case. If this was the case, it wouldn’t just be ubuntu.