Hacker News Reader

Hacker News

Comment by Someone | Hacker News Reader

Full thread

Someone

Earlier articles in this ongoing series of “how to name things”:

- September 2016: Introducing .NET Standard (https://devblogs.microsoft.com/dotnet/introducing-net-standa...)

- May 2019: .NET Core is the Future of .NET (https://devblogs.microsoft.com/dotnet/net-core-is-the-future...)

- May 2019: Introducing .NET 5 (https://devblogs.microsoft.com/dotnet/introducing-net-5/)

(Yes, the last two are from the same month, even day. The second one is consistent with this article)

I may have missed a few episodes.

View on HN

I don't see the problem with the last two you listed, seeing as right near the top of the article it says -

.NET 5 = .NET Core vNext

They are basically taking .NET Core and getting rid of the Core aspect of the name since it will be the only actively developed version of .NET going forward.

Omfg, the hours I've wasted searching for netframework answers, and all the search results are netcore. Because search engines prefer newer, and nobody adds "framework" to their questions.

I've had the opposite problem more than once. ;-) When .Net Core 3.x was in development, OMG was it hard to actually find examples of how to do certain things.

At least .Net Core (soon 5) is easier to target containers (Docker) with.

Speaking of "how to name things," how is target framework name abbreviated to TFM?

Edit: found it--the "M" is for moniker.

So we can mentally translate "TFM" as "name" in nearly all realistic contexts:

"To better reflect this, we’ve updated the target framework names (TFMs)"

becomes "To better reflect this, we’ve updated the names"

This whole .net stuff is actually fairly simple. People could easily grasp something like:

.Net framework (the same thing that MS always had)

A new named cross platform framework. Not just another .Net derivative.

And a new name for the standard. Something like the Common .Net API.

That would have pretty much eliminated all confusion.

Instead they went with

.Net Framework

.Net Core

.Net standard

.Net {version_num}

Unless you're old enough to remember when everything was named .NET (e.g. Office.NET, Windows.NET).

It was a very very short time.

It was a few years, but that's MS pattern. Now days everything is either o365 or Azure branded.

this is so confusing. .net core

.net (before core)

.netstandard 2.1

.net 5

what a joke. This coming from someone who used to work as dev in .NET

It's not THAT bad. You're conflating a bunch of stuff. If you're interested just take some time and read up on it. The roadmap is clearly explained on docs.microsoft.com.

i would also like to get off the bus

What’s so weird is that DirectX has an entirely terrestrial naming system and .NET refuses to follow its example.

.net ultimate incoming

With .NET 5 things are going back to a "check the version number" naming system though. 5 is greater than .NET Core 3.x, .NET Framework 4.x, and .NET Standard 2.x, you can pretty much forget what Core/Framework/Standard entirely mean as soon as you can upgrade to 5. (And the next version is .NET 6.) It's one version number left now.

(Also, DirectX tried to version number individual components at various points in its history so even DirectX "naming" isn't that straightforward at certain points in time in the past.)

Reply on news.ycombinator.com