• dazzledbeans @lemmy.world
    link
    fedilink
    arrow-up
    31
    ·
    3 days ago

    I was going through azure web app services, who the f names this things.

    Automatic scaling and autoscale are two different things. WTF.

    • floofloof@lemmy.ca
      link
      fedilink
      arrow-up
      27
      ·
      3 days ago

      Microsoft always has 20 variants of the same name for maximal confusion. It’s deep in their culture.

        • Faalangst_26@lemm.ee
          link
          fedilink
          arrow-up
          6
          ·
          3 days ago

          Also true the other way around, things that sound like the same but are actually different:

          .NET Core, .NET Framework, .NET Standard, .NET

          Bonus points for Microsoft also often using the term “framework” for labeling .NET (Core). And then there of course also is ASP.NET because of course.

          Just great.

          • Lv_InSaNe_vL@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            2 days ago

            I thought at some point they dropped all those and it’s just .net now?

            Edit: nope, you’re right. Here’s the explanation from Microsoft

            There are multiple variants of .NET, each supporting a different type of app. The reason for multiple variants is part historical, part technical.

            .NET implementations:

            • .NET Framework – The original .NET. It provides access to the broad capabilities of Windows and Windows Server. It is actively supported, in maintenance.
            • Mono – The original community and open source .NET. A cross-platform implementation of .NET Framework. Actively supported for Android, iOS, and WebAssembly.
            • .NET (Core) – Modern .NET. A cross-platform and open source implementation of .NET, rethought for the cloud age while remaining significantly compatible with .NET Framework. Actively supported for Linux, macOS, and Windows.