The future of .NET Standard

#1

Post by flipchart » Mon, Sep 21, 2020, 2:27 PM UTC

The future of .NET Standard
devblogs.microsoft.com

Re: The future of .NET Standard

#2

Post by Someone » Mon, Sep 21, 2020, 2:41 PM UTC

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.

Re: The future of .NET Standard

#3

Post by akmittal » Mon, Sep 21, 2020, 2:46 PM UTC

Microsoft is making lots of performance improvements on .Net Core side. It seem to be lot faster than Java now. With .net core being open source and Cross Platform I think it is still not able to take Javas marketshare. https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Re: The future of .NET Standard

#4

Post by nightski » Mon, Sep 21, 2020, 2:57 PM UTC

Someone wrote: post #2

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 mo…

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.

Re: The future of .NET Standard

#5

Post by SloopJon » Mon, Sep 21, 2020, 3:12 PM UTC

Someone wrote: post #2

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 mo…

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

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

Re: The future of .NET Standard

#6

Post by samfisher83 » Mon, Sep 21, 2020, 3:57 PM UTC

akmittal wrote: post #3

Microsoft is making lots of performance improvements on .Net Core side. It seem to be lot faster than Java now. With .net core being open source and Cross Platform I think it is still not able to take Javas marketshare. https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Plus Oracle is being shady with their licensing terms.

Re: The future of .NET Standard

#7

Post by kasperni » Mon, Sep 21, 2020, 3:58 PM UTC

akmittal wrote: post #3

Microsoft is making lots of performance improvements on .Net Core side. It seem to be lot faster than Java now. With .net core being open source and Cross Platform I think it is still not able to take Javas marketshare. https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Some of the .Net examples literal calls into native code.

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

vs

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

That is hardly a fair comparison.

Re: The future of .NET Standard

#8

Post by kasperni » Mon, Sep 21, 2020, 4:00 PM UTC

samfisher83 wrote: post #6

akmittal wrote: post #3

Microsoft is making lots of performance improvements on .Net Core side. It seem to be lot faster than Java now. With .net core being open source and Cross Platform I think it is still not able to take Javas marketshare. https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Plus Oracle is being shady with their licensing terms.

Shady in what way? OpenJDK is licensed under GPL2 with linking exception.

Re: The future of .NET Standard

#9

Post by grezql » Mon, Sep 21, 2020, 4:13 PM UTC

Someone wrote: post #2

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 mo…

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

Re: The future of .NET Standard

#10

Post by karianna » Mon, Sep 21, 2020, 4:15 PM UTC

kasperni wrote: post #8

samfisher83 wrote: post #6

Earlier quoted context omitted.

Plus Oracle is being shady with their licensing terms.

Shady in what way? OpenJDK is licensed under GPL2 with linking exception.

MSFT Employee here who came in via last year’s jClarity acquisition (yes Microsoft now has a Java Engineering Group!). Oracle change the licensing terms on its Oracle JDK (which was the default JDK most of the world used) to something more commercial which some folks thought was it communicated well enough.

There are a ton of free in beer and free in use options. You can look at adoptopenjdk.net for the broadest community led one or azul Zulu for the one that’s been around since even before Oracle made their change