5 ms·
Earlier articles in this ongoing series of “how to name things”: - September 2016: Introducing .NET Standard (https://devblogs.microsoft.com/dotnet/introducing
by Someone 6y ago
Earlier articles in this ongoing series of “how to name things”:
- September 2016: Introducing .NET Standard (https://devblogs.microsoft.com/dotnet/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-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/ 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.
- nightski 6y agoI 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.
- grezql 6y agothis 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
- crispyambulance 6y agoIt'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.
- juststeve 6y agoi would also like to get off the bus
- SloopJon 6y agoSpeaking of "how to name things," how is target framework name abbreviated to TFM? Edit: found it--the "M" is for moniker.
- andybak 6y agoSo 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"
- jimbob45 6y agoWhat’s so weird is that DirectX has an entirely terrestrial naming system and .NET refuses to follow its example.
- oceanswave 6y ago.net ultimate incoming
- mlvljr 6y agoNET Last. NET Eternal. Dot Nyet :/
- WorldMaker 6y agoWith .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.)
- daxfohl 6y agoOmfg, 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.
- tracker1 6y agoI'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.
- deleted 6y ago[deleted]
- addicted 6y agoThis 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}