• Kogasa@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    I really don’t think it’s that bad. The only weird thing is .NET Core becoming just .NET in version 5.

    • dan@upvote.au
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Not too weird… It’s the “one true .NET version” now. The legacy .NET Framework had a good run but it’s not really receiving updates any more.

      • Kogasa@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        I have no complaints about just calling it .NET. The distinction between .NET and .NET Framework isn’t much of a problem. It’s the fact that .NET and .NET Core aren’t actually different that’s odd. It underwent a name change without really being a different project, meanwhile the Framework -> Core change was actually a new project.

        • Lmaydev@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          7 months ago

          Actually they are different.

          .Net core, mono and xamarin used to be completely separate and slightly incompatible runtimes.

          They have all been unified under .Net so c# (and other .net languages) will run exactly the same on each.

          So the coreclr runtime still exists but you no longer need to target it specifically.