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

.NET 6 Released

devblogs.microsoft.com

Post reply on HN
Print view View original

71–80 of 428 posts

Re: .NET 6 Released

#71

Post by goto11 »

kreeben wrote: post #4

>> ASP.NET Core in .NET 6. I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused. Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.

The naming really is confusing. "Core" was the keyword for several semi-independent projects.

There is .Net Core, which was a rewrite of the .Net runtime to make it platform independent.

Then there is ASP.Net Core is which is a rewrite of the ASP.Net web stack. Despite the name, this was not initially dependent on .Net Core platform, it could run on both .Net Framework and .Net Core.

ASP.Net Core is the only web framework running on .Net Core though, the old ASP.Net framework is not ported to .Net Core. So to answer your question, no, there is not a non-core asp.net running on the .Net Core platform.

Then there is EF Core which was a rewrite of Entity Framework. Again, this was not initially dependent on .Net Core, although later versions is.

Basically "Core" just means "new backwards-incompatible rewrite".

Re: .NET 6 Released

#72

Post by dustinmoris »

dschuessler wrote: post #33
phillipcarter wrote: post #12

Earlier quoted context omitted.

> Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? Yep! > I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage. .NET 5 was the next evolution of .NET Core. There was no great merging of legacy .NET Framework into the .NET Core branch or something like that. It saw a bunch of foundational stuf…

Microsoft branding is terrible. My only point of contact with it is Visual Studio Code which is different from Visual Studio which is different from Visual Studio for Mac. There was a brief period of time after I recognized that .NET really works on all platforms without proprietary stuff and before the `dotnet watch` desaster in which I was at least curious about .NET. But even then I never fully figured out how .NE…

> Microsoft branding is terrible.

Agreed.

> I never fully figured out how .NET, .NET Core, ASP.NET, .NET Framework, .NET MAUI and the kitchen sink relate to each other.

You're not the only one who is massively confused about everything that is labelled .NET or Core.

If anyone else is struggling, I recommend this (I wrote it):

https://dusted.codes/dotnet-basics

Re: .NET 6 Released

#73

Post by a_lost_needle »

kbd wrote: post #51

Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…

Low/No code solutions are really eating the lunch of where C# was useful in large internal apps. I use it because F#, but it’s getting harder to sell that.

Re: .NET 6 Released

#74

Post by AtNightWeCode »

ziml77 wrote: post #46
SloopJon wrote: post #42

> Supported for three years as the latest long term support (LTS) release. This is the first thing I look for in these announcements. .NET 6 is the successor to .NET Core 3.1.

I've been waiting for .NET 6 for the past year for the long term support. As much as I wanted to use .NET 5, I figured it would be best to only use LTS releases in production.

I never run anything else than LTS in production. The in-between versions have basically been beta quality since .NET 1-preview.

Re: .NET 6 Released

#75

Post by spaetzleesser »

T-A wrote: post #66
kbd wrote: post #51

Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…

MAUI, maybe? https://github.com/dotnet/maui

Based on past experience it’s a very very very bad idea to rely on anything that MS does in the desktop development area. I would be shocked if MAUI wasn’t dead in five years.

Re: .NET 6 Released

#76

Post by elorant »

jekude wrote: post #34

As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET. Perhaps this is indicative of the larger Microsoft ecosystem, but it feels like my peers at university and in the industry tend to stay far away from .NET for personal projects, etc. Why is this?

Probably because of licensing costs. Take for example SQL Server. If you want to use it on a server with more than 128GB or RAM you have to get the enterprise version which is licensed per core and the cost is in the thousands per each core pair. Sure, you get a discount, but still the price is steep.

Re: .NET 6 Released

#77

Post by sedatk »

lbriner wrote: post #3

I would personally prefer you to fix the multitude of things that don't work well in Visual Studio and library issues that are continually pushed back as "won't fix" or "upgrade to .Net5/6" as opposed to always racing forwards to the horizon. Even those of us who are actively migrating applications are stuck with web forms, netfx and dotnet core 2/3 and will be for years, so it would be nice that we felt some love ra…

It's not perfect but MS has been investing in a scheme to make upgrades as easy as possible for the last five years, .NET Standard being the prime example. This way, we've been able to migrate our project progressively while keeping it up to date. We've been able to use .NET Core versions of libraries as long as they support .NET Standard 2.0. This is way better than "migrate fully or die".

Re: .NET 6 Released

#78

Post by UglyToad »

kbd wrote: post #51

Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…

Depends what you're after. The only correct advice for "what to do a project in" if you're looking to ship and/or make money is "use what you know" so any advice beyond that is heavily contextual.

There is no killer feature for .NET I think. That's why it's a hard sell. I think its sales pitch is more or less parallel to Java (though I prefer C# to Java and VS to IntelliJ).

Do you want a statically typed, extremely fast, cross-platform language with a comprehensive standard library and huge ecosystem of 3rd party packages with almost unrivalled devX (Rider on non-Windows OSes) and streamlined packaging and deployment that allows you to scale from single person PoC to large team development within the same codebase with no additional overhead?

I'd note that it's a bit of a jack-of-all-trades when it comes to desktop and ML. The ML.NET package keeps getting better but for those areas where there's an obvious standard, e.g. Python for ML, you may as well use the standard for that thing. The desktop story continues to disappoint and I'd advise people to steer clear of desktop unless they want a nasty surprise. But for web applications I'd not want to use anything else.

Re: .NET 6 Released

#79

Post by icey »

kbd wrote: post #51

Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…

C# is fast and .NET core is cross-platform. It's good for games, web, and mobile development. F# is a great functional programming language. There are fun tools like SignalR (easy websockets), Blazor (write C# and run it in the browser through WASM), and LINQ (built right into the language and allows you to query objects like a database).

Toplevel programs should make it easier to experiment with C# if you're interested. We also have first-class support for C# commands in https://ab.bot if you just want to play around with the language and make a fun Slack bot or something, although it might take us a week or so to get move up to .NET 6.

Re: .NET 6 Released

#80

Post by spaetzleesser »

dschuessler wrote: post #33
phillipcarter wrote: post #12

Earlier quoted context omitted.

> Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? Yep! > I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage. .NET 5 was the next evolution of .NET Core. There was no great merging of legacy .NET Framework into the .NET Core branch or something like that. It saw a bunch of foundational stuf…

Microsoft branding is terrible. My only point of contact with it is Visual Studio Code which is different from Visual Studio which is different from Visual Studio for Mac. There was a brief period of time after I recognized that .NET really works on all platforms without proprietary stuff and before the `dotnet watch` desaster in which I was at least curious about .NET. But even then I never fully figured out how .NE…

Agreed 100%. Even seasoned .NET devs can’t tell what all this stuff means and what the implications are. I wonder if anybody at MS really knows.
Post reply on HN