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

Understanding the .NET ecosystem: The evolution of .NET into .NET 7

andrewlock.net

Post reply on HN
Print view View original

91–100 of 357 posts

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#91

Post by zigzag312 »

Imagine it like a Git repo.

Old .NET Framework was a main, Windows only, branch of .NET.

At tag "v4.x", a new branch named 'Core' was created. Core was a multiplatform version of .NET.

There were three tags in the Core branch: v1, v2 & v3.

Then Core jumped from v3 to v5 and was merged back into the main branch. ".NET Core" has replaced ".NET Framework". Also, v5 dropped 'Core' from the name and was named just ".NET 5".

Development now happens on the main branch and has already reached tag v7. A new tag is created each year.

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#92

Post by mattmanser »

jiggawatts wrote: post #62

My big problem with .NET is that a lot of line-of-business apps were written using ASP.NET Web Forms, but there is no upgrade path other than “rewrite most of it”. It feels like the pain everyone went through upgrading from Python 2 to Python 3. It also doesn’t help that .NET Framework has its support cycle tied to the OS, and hence is 10+ years. This means that businesses can be lazy and just leave these old apps to…

The writing was on the wall a long, long time ago!

These companies had 15 years to do it. And it was fairly easy to get webforms + MVC running side-by-side on the same site so you could gradually migrate.

Too late for that now though, you can't run webforms + MVC Core side-by-side.

You could put a load balancer in front of the old app and start moving end points to a new code base.

It's akin to moaning that MS haven't got an upgrade path from IE7. Or your Adobe Air app has stopped working.

On the plus side, doesn't 4.7 still have a huge support window because it's tied to one of the windows server versions?

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#93

Post by evntdrvn »

lp0_on_fire wrote: post #27

I love the new dotnet ecosystem and use it professionally but am I the only one who thinks two years isn’t long enough for a “long term support” release? Obviously you’ll be able to run older versions of the framework so long as the underlying OS supports it but depending what type of environment you’re in this means you’re likely going to have to update perfectly working applications every two years. Do I think that…

The upgrade process from 5 to 6 to 7 has been a total breeze, and I’expect things to continue in that matter.

There was a massive amount of churn between the introduction of .NET Core and Core 3, then 3 to 5 was quite a bit less so, and since then it’s been a non-issue. Pretty much just flip a version flag and get new features.

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#94

Post by simooooo »

tiffanyh wrote: post #19
pyjarrett wrote: post #16

Earlier quoted context omitted.

1. .NET "Core" ... I tell myself "C is for Cross platform." This is usually what people seem like they mean now when they talk about ".NET". 2. .NET "Framework" ... I tell myself "F is for Former." This is the older, Windows specific version. 3. .NET "Standard" ... I tell myself "S is for Specification." This is just the spec which defines what Core and Framework must implement.

That’s super helpful, thank you. Where it still gets a bit murky is: > “ .NET has many different implementations, including the .NET Framework, Mono, and Unity. Each of these is a separate platform with separate Base Class Libraries (BCLs) and app models. .NET Core is another separate platform.”

You don’t really interact with or care about mono as A normal c# dev

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#95

Post by Kwpolska »

Accacin wrote: post #72

Odd question maybe, my company uses C# and I've been picking up more backend responsibilities. However, I'm a Linux and Neovim user. I do have Windows and Visual Studio available but I just find it awkward. Is anyone here having success with Linux and Neovim for C#? Even trying to learn more about the language is awkward as so many resources go straight into VS.

https://github.com/OmniSharp/Omnisharp-vim is a thing, but I don’t know how good it is. I would probably go with VSCode or Rider (and their respective Vim plugins), as they are quite productive for .NET.

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#97

Post by simooooo »

evntdrvn wrote: post #93
lp0_on_fire wrote: post #27

I love the new dotnet ecosystem and use it professionally but am I the only one who thinks two years isn’t long enough for a “long term support” release? Obviously you’ll be able to run older versions of the framework so long as the underlying OS supports it but depending what type of environment you’re in this means you’re likely going to have to update perfectly working applications every two years. Do I think that…

The upgrade process from 5 to 6 to 7 has been a total breeze, and I’expect things to continue in that matter. There was a massive amount of churn between the introduction of .NET Core and Core 3, then 3 to 5 was quite a bit less so, and since then it’s been a non-issue. Pretty much just flip a version flag and get new features.

Yep 6 to 7 was just changing a 6 to a 7 in a project file

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#98

Post by bmitc »

rbanffy wrote: post #11

I am mostly a Python person, but I must confess I'm impressed by both modern .NET and Java's Spring Boot. I architect for two teams, one using Java, the other using C#, for building services and the amount of boilerplate code, that used to be a huge turnoff for me, has been impressively reduced. There's still a lot, but it's now more or less comparable to what you'd expect you'd end up with on a similar app built on,…

I'd recommend taking a look at F#.

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#99

Post by Kwpolska »

cm2187 wrote: post #63
jve wrote: post #51

Earlier quoted context omitted.

> Not breaking your users used to be a laudable goal of the .net team. I miss it Is it that bad once you are on .NET Core? Asking as someone still on Framework. Framework -> Core ofcourse is breaking, what did you expect when going cross platform and totally rearchitected?

I am sure cross platform is useful to some users but not to me. So to me it's all breaking changes for little benefits. I am not saying .net core is bad, just that the migration is a lot of work. And you need to disable all sorts of compiler warnings unless you are ready to rewrite pretty much all your code to make it nullable ref type friendly. And some day those warnings will be errors.

> And you need to disable all sorts of compiler warnings unless you are ready to rewrite pretty much all your code to make it nullable ref type friendly.

Not really. Just disable nullability checking — you can do it project-wide by removing the Nullable tag from your .csproj, and you can continue ignoring nullability.

> And some day those warnings will be errors.

[citation needed]. A lot of code is written without nullability in mind. That includes the .NET Core BCL, AFAIK.

Re: Understanding the .NET ecosystem: The evolution of .NET into .NET 7

#100

Post by evntdrvn »

pyjarrett wrote: post #50
pavelbr wrote: post #45

Earlier quoted context omitted.

Seems to be about the same as it's ever been. Still being updated and worked on, and still very few people use it.

> Still being updated and worked on It is, hands down, my best experience working in a functional language. I do hobby work in it, and it seems super nice, but I'm not sure where everyone is. > still very few people use it. Looking at a chart of GitHub and StackOverflow usage[1], OCaml/F# seem almost steady compared to the other functional languages, my suspicion is that Rust absorbed a lot of programmers looking for…

yeah I’d say usage has been steady, maybe with a slight uptick in interest it feels like.

It’s a great platform, in some ways it’s like a secret weapon…

I joke that F# is kinda “easy-button Rust” lol

Post reply on HN