this post was submitted on 07 Feb 2024
1623 points (99.3% liked)

Programmer Humor

19623 readers
2719 users here now

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.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
1623
dotnet developer (programming.dev)
submitted 9 months ago by JPDev@programming.dev to c/programmer_humor@programming.dev
124 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] kogasa@programming.dev 8 points 9 months ago (1 children)

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 2 points 9 months ago (1 children)

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 2 points 9 months ago (2 children)

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.

[–] dan@upvote.au 1 points 9 months ago* (last edited 9 months ago) (1 children)

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 :)

[–] kogasa@programming.dev 1 points 9 months ago

Yes... But ASP.NET Core kept the branding. Thus "Core" still exists, concurrently with the regular ".NET."

[–] Lmaydev@programming.dev 1 points 7 months ago* (last edited 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.