Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The future of .NET Standard

devblogs.microsoft.com

Post reply on HN
Print view View original

31–40 of 84 posts

Re: The future of .NET Standard

#31

Post by golergka »

qz2 wrote: post #11

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

> most schizophrenic platform

> danger money

In my experience, these often go hand-in-hand. Also, never heard 'danger money' and absolutely love it, thanks.

Re: The future of .NET Standard

#33

Post by cptskippy »

addicted wrote: post #30
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 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).

Re: The future of .NET Standard

#34

Post by qz2 »

goto11 wrote: post #27
qz2 wrote: post #11

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

Web forms?

Nope. An ASP.Net MVC project dragged through since CTP versions.

Re: The future of .NET Standard

#35

Post by crispyambulance »

grezql wrote: post #9
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

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.

Re: The future of .NET Standard

#36

Post by bookshelf976 »

qz2 wrote: post #11

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

What do you mean by five different variants? Also, what are the chunks of the ecosystem that were abandoned? Web Forms? Silverlight? UWP?

Microsoft has shown an amazing ability to modernize and improve the platform without dragging baggage around from one version to the next.

We just took an ASP.NET MVC web app developed in 2005 for Windows/IIS and shipped it on linux using .NET core— the conversion took 1 developer just 2 days.

Re: The future of .NET Standard

#37

Post by apta »

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

golang isn't really a threat. It's a weak language with a very messy ecosystem. They don't even have proper versioning figured out, not to mention a proper package manager.

Re: The future of .NET Standard

#38

Post by kyberias »

cptskippy wrote: post #33
addicted wrote: post #30

Earlier quoted context omitted.

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.

Re: The future of .NET Standard

#39

Post by Hickfang »

The future of the .NET “Standard” .. it'll be a continously moving target, making it near impossible to clone ;]

Of course that'll mean developers are for ever playing catch-up, rewriting code at more expence.

Re: The future of .NET Standard

#40

Post by iso8859-1 »

yAak wrote: post #20

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…

What do you mean by "native-client"? Google Native Client?
Post reply on HN