• OneCardboardBox@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    214
    arrow-down
    6
    ·
    1 年前

    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@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      66
      arrow-down
      5
      ·
      1 年前

      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.

            • Octopus1348@lemy.lol
              link
              fedilink
              arrow-up
              7
              ·
              1 年前

              I once heard some YouTuber say Windows uses \ in path names instead of / like everyone else because Microsoft thinks backwards.

              • danA
                link
                fedilink
                arrow-up
                5
                ·
                edit-2
                1 年前

                As what often happens, using \ for paths is for backwards compatibility.

                Neither CP/M nor MS-DOS 1.0 had folders. When folders were added in MS-DOS 2.0, the syntax had to be backwards compatible. DOS already used forward slashes for command-line options (e.g. DIR /W) so using them for folders would have been ambiguous - does that DIR command have a /W option, or is it viewing the contents of the W directory at the root of the drive? Backslashes weren’t used for anything so they used them for folders.

                This is the same reason why you can’t create files with device names like con, lpt1, and so on. DOS 2.0 has to retain backwards compatibility with 1.0 where you could do something like TYPE foo.txt > LPT1 to send a document to a printer. The device names are reserved globally so they can work regardless of what folder you’re in.

            • Honytawk@lemmy.zip
              link
              fedilink
              arrow-up
              4
              arrow-down
              2
              ·
              1 年前

              Well, better to be backwards with backwards compatibility than to just be backwards.

              looks at Apple

        • intensely_human@lemm.ee
          link
          fedilink
          arrow-up
          2
          ·
          1 年前

          it could’ve just been windows nine. or any other word that isn’t a number

          But “nine” is a word that is a number

      • puttputt@beehaw.org
        link
        fedilink
        arrow-up
        16
        ·
        1 年前

        The reason they checked that it started with “Windows 9” was because it worked for “Windows 95” and “Windows 98”

      • activ8r@sh.itjust.works
        link
        fedilink
        arrow-up
        12
        arrow-down
        4
        ·
        1 年前

        It makes sense why they did it, but their messed up versioning was the cause to begin with. You should always assume Devs will cut corners in inappropriate ways.

      • dev_null@lemmy.ml
        link
        fedilink
        arrow-up
        9
        arrow-down
        1
        ·
        edit-2
        1 年前

        An often repeated urban legend that has no basis in reality. Software checking the version of Windows gets “6.1” for Windows 7 and “6.2” for Windows 8. The marketing name doesn’t matter and is different.

      • danA
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        1 年前

        some legacy software checked if the OS name began with “Windows 9” to differentiate between 95 and future versions.

        This is a myth. Windows doesn’t even have an API to give you the marketing name of the OS. Internally, Windows 95 is version 4.0 and Windows 98 is 4.1. The API to get the version returns the major and minor version separately, so to check for Windows 95 you’d check if majorVersion = 4 and minorVersion = 0.

        Edit: This is the return type from the API: https://learn.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-osversioninfoexa

      • dfyx@lemmy.helios42.de
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        1 年前

        And for the same reason they went straight from 2.1 3.x to 5.0 when they renamed .Net Core to just .Net. Versions 3.x and 4.x would have been too easy to confuse (either manually or programmatically) with the old .Net Framework versions that were still in use, especially for Desktop applications.

        • Wrrzag@lemmy.ml
          link
          fedilink
          arrow-up
          5
          ·
          1 年前

          Because it checks if the version starts with the string “Windows 9*”, not wether the number is less than 9.

          • danA
            link
            fedilink
            arrow-up
            2
            ·
            1 年前

            This is a myth - code that checks the version number uses the internal version number, which is 4.0 for Windows 95.

      • Ziixe@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        1 年前

        I was about to say that most apps should check the NT number but then I remembered that until XP it wasn’t common to run a NT system, but then I remembered NT 4 existed basically in the same timeframe as 95 did, and even if the argument went to “it’s a 9x application”, shouldn’t these OSes at least have some sort of build number or different identifier systems? Because as I said NT systems were around, so they would probably need a check for that

    • XTornado@lemmy.ml
      link
      fedilink
      arrow-up
      18
      ·
      1 年前

      .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
          arrow-up
          2
          ·
          edit-2
          1 年前

          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
            arrow-up
            3
            ·
            1 年前

            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

    • Pfnic@feddit.ch
      link
      fedilink
      arrow-up
      12
      ·
      1 年前

      I have the same issue with Java. Oracle JDK, Open JDK or some other weird distribution? Enteprise Servers or a Framework like Springboot? It’s always easier if you’re familiar with the technology.

    • Kogasa@programming.dev
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      1 年前

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

      • danA
        link
        fedilink
        arrow-up
        2
        ·
        1 年前

        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
          2
          ·
          1 年前

          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.

          • danA
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 年前

            It underwent a name change without really being a different project

            The name difference was only to differentiate the legacy .NET Framework with the new .NET Core while both were being developed concurrently. They never intended to keep the “Core” suffix forever. .NET Core had a lot of missing APIs compared to .NET Framework 4.5., and “.NET 1.0” would have been ambiguous. It was to signify that it was a new API that isn’t fully compatible yet.

            Once .NET Core implemented nearly all the APIs from the legacy .NET Framework, the version numbers were no longer ambiguous (starting from .NET 5.0), and the legacy framework wasn’t used as much as it used to be, it made sense to drop the “Core” suffix :)

          • Lmaydev@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 年前

            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.

      • coloredgrayscale@programming.dev
        link
        fedilink
        arrow-up
        8
        ·
        1 年前

        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.

      • Rev. Layle@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 年前

        The reasoning it was to not confuse with .net framework 4.x series, and since they went beyond 4.x, it’s just .net now. I believe .net core moniker was to explicitly distinguish is from framework versions.

        It didn’t help the confusion at all, tch. Being a .net guy since 1.0, you just figure it out eventually

    • labsin@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      1 年前

      They also couldn’t call it “.Net Core 4” so they called it “.Net 5”

      Will they keep skipping numbers or start thinking about not naming everything the same.

    • Vladkar@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      1 年前

      Remember when Nintendo was panned for the name “Wii U”, and Microsoft saw that and said “hold my beer”

    • Lmaydev@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 年前

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

      Microsoft is so bad at naming things!

  • envelope@kbin.social
    link
    fedilink
    arrow-up
    156
    arrow-down
    2
    ·
    1 年前

    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.

  • Gork@lemm.ee
    link
    fedilink
    arrow-up
    136
    ·
    1 年前

    No, you’ll need to contact Kim Dotcom. I am merely Kim Dotnet.

    • neutron@thelemmy.club
      link
      fedilink
      arrow-up
      28
      ·
      1 年前

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

      • danA
        link
        fedilink
        arrow-up
        10
        ·
        edit-2
        1 年前

        .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.

        • NegativeInf@lemmy.world
          link
          fedilink
          arrow-up
          7
          ·
          1 年前

          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.

          • danA
            link
            fedilink
            arrow-up
            5
            ·
            1 年前

            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.

          • Zangoose@lemmy.one
            link
            fedilink
            arrow-up
            5
            ·
            1 年前

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

          • Kogasa@programming.dev
            link
            fedilink
            arrow-up
            2
            ·
            1 年前

            Not an intern, but this week I’ve unraveled some mysteries in ASP.NET MVC 5 (framework 4.8). Poked around the internals for a while, figured out how they work, and built some anti-spaghetti helpers to unravel a nested heap of intermingled C#, JavaScript, and handlebars that made my IDE puke. I emulated the Framework’s design to add a Handlebars templating system that meshes with the MVC model binding, e.g.

            @using (var obj = Html.HandlebarsTemplateFor(m => m.MyObject))
            {
              Name: obj.TemplateFor(o => o.Name)
            }
            

            and some more shit to implement variable-length collection editors. I just wish I could show all this to someone in 2008 who might actually find it useful.

          • Lmaydev@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 年前

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

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

        • neutron@thelemmy.club
          link
          fedilink
          arrow-up
          2
          ·
          1 年前

          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.

  • Sanctus@lemmy.world
    link
    fedilink
    English
    arrow-up
    72
    ·
    1 年前

    I can, but due to the extra strains involved the price of this contract will increase.

    • nelly_man@lemmy.world
      link
      fedilink
      English
      arrow-up
      68
      ·
      edit-2
      1 年前

      It was an interview with Jonathan Swan about COVID-19 where Trump had a bunch of papers with graphs trying to show that the US was doing well with cases. The paper he handed over showed the rates of deaths per case (though Trump didn’t seem to understand the graph), and Swan was asking him about the high rate of deaths in the US when looking at the total population of the country.

      https://youtu.be/NmrEfQG6pIg

  • twopi@lemmy.ca
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    8
    ·
    1 年前

    Well .NET is dead now so I guess .COM and .ORG are dead too?

  • JoShmoe@ani.social
    link
    fedilink
    arrow-up
    5
    ·
    1 年前

    Can you spot the error? Johnson went to the trump organization for a professional field.

  • ursakhiin@beehaw.org
    link
    fedilink
    arrow-up
    7
    arrow-down
    3
    ·
    1 年前

    It’s been my experience that the .NET developer will miss the actual statement and take it as an assault on .NET being the best solution for every use case.

  • intensely_human@lemm.ee
    link
    fedilink
    arrow-up
    3
    ·
    1 年前

    This is one of the funniest meme templates because it’s based on one of the funniest moments in media history.

  • Destide@feddit.uk
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 年前

    Yes but I’ll l need to charge more as they require disclosure specific equipment

  • 🔻Sleepless One🔻@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 年前

    I use .NET for my job. My team shifted to a lot of frontend work with react for about a year when the lastest .NET was .NET 5. Barely a year later after not touching it the latest version was .NET 7. Ridiculous.