• @OneCardboardBox@lemmy.sdf.org
    link
    fedilink
    English
    61 year ago

    Sorry, what’s .Net again?

    The runtime? You mean .Net, or .Net Core, or .Net Framework? Oh, you mean a web framework in .Net. Was that Asp.Net or AspNetcore?

    Remind me why we let the “Can’t call it Windows 9” company design our enterprise language?

    • Trailblazing Braille Taser
      link
      fedilink
      41 year ago

      Can’t call it Windows 9

      But that actually made sense! They care about backwards compatibility.

      For those not in the know: some legacy software checked if the OS name began with “Windows 9” to differentiate between 95 and future versions.

    • @XTornado@lemmy.ml
      link
      fedilink
      21 year ago

      .net core is not a thing anymore in case somebody it’s not aware, now is just .net. (unless you use really old version of course).

        • @XTornado@lemmy.ml
          link
          fedilink
          0
          edit-2
          1 year ago

          Well the repo link yes… create a new repo and migrate everything… just so the url doesn’t say core no more it’s quite unnecessary.

          And to be honest actual code is currently under https://github.com/dotnet/dotnet The other links is just for news and docs currently.

          • @kautau@lemmy.world
            link
            fedilink
            11 year ago

            I agree, it was mostly a joke. But as the parent commenter explained, “.net is now dot net” is still confusing. They really should just cut ties with the .net name and start fresh. “.net is now MS Interop Framework” or some such. Adopt more sane server versioning moving forward, so searching for information isn’t so wild across all the possible variations and versions of .net, dot net core, dot net framework, asp.net, etc

    • @Lmaydev@programming.dev
      link
      fedilink
      11 year ago

      .Net is both the umbrella term for the entire ecosystem and the new runtime haha

      Microsoft is so bad at naming things!

    • Kogasa
      link
      fedilink
      11 year 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
        11 year 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
          link
          fedilink
          11 year 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
            1
            edit-2
            1 year 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.

      • May I introduce you to Usb 3.x renaming?

        3.0, 3.1Gen1, 3.2Gen1, 3.2Gen1x1 are the 5Gbps version.

        3.1Gen2, 3.2Gen2, 3.2Gen1x2, 3.2Gen2x1 are the 10Gbps version.

  • envelope
    link
    fedilink
    31 year ago

    Given that .net was a TLD long before the framework came out, it was a stupid thing to name it. Caused confusion and the inability to Google things right away.

        • @kameecoding@lemmy.world
          link
          fedilink
          11 year ago

          At least they don’t control the most popular code hosting site along with the most popular code editing software, right? Right?

        • @eerongal@ttrpg.network
          link
          fedilink
          01 year ago

          I mean, blob (and object storage in general) has been used as a term for a long time. It isn’t particularly new, and MS didn’t invent it.

          • @xmunk@sh.itjust.works
            link
            fedilink
            1
            edit-2
            1 year ago

            That’s sort of the problem. It’s easy to Google S3 since it’s a distinct (if obnoxiously short) term. Blob is already an overloaded term.

            An example of a great name from Microsoft is Excel, it’s relatively short but meaningless so if you Google “Excel Sum” you’ll get wonderful results… “Blob Get” is going to get you a lot of random stuff.

            Edit: the top result for blob get is accurate on Google but you’ll also quickly see this result from that site we all hate:

            Need help! How do I get the blob fish, basking shark and dwarf whale?

    • @neutron@thelemmy.club
      link
      fedilink
      01 year ago

      And then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.

      • @dan@upvote.au
        link
        fedilink
        1
        edit-2
        1 year ago

        .NET Core doesn’t exist any more. It’s just .NET now. I think that changed around the release of .NET 5?

        The classic version is mostly legacy at this point too.

        • @neutron@thelemmy.club
          link
          fedilink
          11 year ago

          My workplace insists on using dot net classic to recreate a twenty years old VB app that should be able to drink, vote, and drive.

          Please send help. SQL queries are a spaghetti mess and all the original devs are probably gone or dead.

        • @NegativeInf@lemmy.world
          link
          fedilink
          01 year ago

          Just because it’s no longer supported doesn’t mean there’s not some poor intern refactoring spaghetti backend in a basement somewhere using it.

          • @dan@upvote.au
            link
            fedilink
            21 year ago

            Sure, but you can still find plenty of info on it by searching for .NET Framework or .NET 4.6. All the documentation is still available. Its just not in the spotlight any more.

          • @Lmaydev@programming.dev
            link
            fedilink
            11 year ago

            It is very much still supported and will be for a very long time.

            You just shouldn’t start any new products using it.

          • @Zangoose@lemmy.one
            link
            fedilink
            01 year ago

            Hi, it’s me, the intern refactoring the spaghetti .NET core backend. I’m not in a basement though. AMA