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

Programmer Humor

19564 readers
635 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 9 months ago (4 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.

[–] [email protected] 2 points 9 months ago (3 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.

[–] [email protected] 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 :)

[–] [email protected] 1 points 9 months ago

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

load more comments (1 replies)
load more comments (1 replies)