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?
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.
The reason they checked that it started with "Windows 9" was because it worked for "Windows 95" and "Windows 98"
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.
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.
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.
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
.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).
Because they have dozens of years of experience! They didn't learn anything from it, but they have it!
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.
I really don't think it's that bad. The only weird thing is .NET Core becoming just .NET in version 5.
I scream silently everytime.
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.
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.
Microsoft names many things stupidly.
Microsoft Azure Blob
(Yes it's a real product they market)
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.
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?
Visual Studio ~~Code~~
To prevent confusion, I call them "VS Code" and "Visual Studio IDE", because if you say Visual Studio, people assume you mean Visual Studio Code.
It's like naming your company x
Like naming a new TLD .zip!
It was pretty smart marketing move. Business people hear 'dot net' and nod wisely. Tech people hear 'dot net' and scrunch their faces. Either way people keep talking about Microsoft Java.
That aligns with their fucked up naming conventions anyway.
No, you'll need to contact Kim Dotcom. I am merely Kim Dotnet.
Ok, but we all should admit: .net is a terrible name.
And then there's .net classic and .net core. Making up two entirely separate names shouldn't be difficult for marketing executives.
.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.
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.
Still better than .dot
I totally agree.socialmedia
I can, but due to the extra strains involved the price of this contract will increase.
How many strains does it take to develop using .net? Are we talking high end or ditch weed?
We talk about 2 bottles of Cuban Rum and 3 packs of sour gummy worms on top of the pay.
Sour? That's top quality, you drive a hard bargain
I can but we’ll need to re negotiate my salary.
Well .NET is dead now so I guess .COM and .ORG are dead too?
.NET is better than ever wdym
But we’re an EDU!!!!
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.
Can you spot the error? Johnson went to the trump organization for a professional field.
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
