The future of .NET Standard • Hacker News Board

Re: The future of .NET Standard

#11

Post by qz2 » Mon, Sep 21, 2020, 4:19 PM UTC

This is the most schizophrenic platform I've ever worked on. I've just spent an hour trying to make something work across the five different variants and web pipelines doing things underneath.

Edit: to be clear we have completely hung legacy stuff which is waiting resources (lots of $$$$ wasted) to port it to later versions of the frameworks because huge chunks of the ecosystem got abandoned by MS and the OSS developers who were supporting it.

On the positive side I'm getting paid danger money now.

Re: The future of .NET Standard

#12

Post by philliphaydon » Mon, Sep 21, 2020, 4:23 PM UTC

kasperni wrote: post #7

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.

https://www.techempower.com/benchmarks/#section=test&runid=4...

These benchmarks are more impressive.

Re: The future of .NET Standard

#13

Post by andybak » Mon, Sep 21, 2020, 4:23 PM UTC

SloopJon wrote: post #5

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.

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"

Re: The future of .NET Standard

#14

Post by stomatomot » Mon, Sep 21, 2020, 4:24 PM UTC

the future of .net? the cemetery lol

they still playing catchup with java when the real threat was GO, now they are behind, and far far behind

Re: The future of .NET Standard

#15

Post by UK-Al05 » Mon, Sep 21, 2020, 4:26 PM UTC

stomatomot wrote: post #14

the future of .net? the cemetery lol they still playing catchup with java when the real threat was GO, now they are behind, and far far behind

Catch up with java? C# .net was always ahead. The advantage java had was the ecosystem.

Re: The future of .NET Standard

#16

Post by thesuperbigfrog » Mon, Sep 21, 2020, 4:27 PM UTC

kasperni wrote: post #7

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.

Agreed. A fair comparison would use .Net code and not call the PCRE2 library. Otherwise, why not use JNI and have it call PCRE2 as well?

Re: The future of .NET Standard

#17

Post by jimbob45 » Mon, Sep 21, 2020, 4:33 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…

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

Re: The future of .NET Standard

#18

Post by daxfohl » Mon, Sep 21, 2020, 4:39 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…

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.

Re: The future of .NET Standard

#19

Post by MikeTheGreat » Mon, Sep 21, 2020, 4:43 PM UTC

"net5.0-windows (and later net6.0-android and net6.0-ios). These TFMs represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific functionality."

Wait - net6.0- is actually net5.0?

Re: The future of .NET Standard

#20

Post by yAak » Mon, Sep 21, 2020, 4:44 PM UTC

As a primarily native-client dev who has developed for most major desktop and mobile platforms, I hope MS achieves it's goal of .NET being a truly solid cross-platform option, but in a way that enables clean and efficient native-code interop.

Having used C++, some insane hand-rolled solutions, PhoneGap/Cordova, Unity, and now Kotlin MPP, I know that the "cross-platform" dream is messy and fraught with disaster, but I've come to really appreciate C# and .NET for day-to-day client dev.