Understanding the .NET ecosystem: The evolution of .NET into .NET 7 • Hacker News Board

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

#21

Post by magicalhippo » Tue, Mar 21, 2023, 10:17 PM UTC

cyral wrote: post #12

Been using .NET for years now for backend web development after having taken a break from C#. It is such an improvement over the old .NET framework. When I started building my first backend with it, I was surprised how much was included and "just worked". Need to add authentication? Few lines. OAuth? Also built in. Response caching? Yes. ORM? EF Core is pretty good. Need to use env variables to override your JSON con…

> ORM? EF Core is pretty good.

We're moving to .Net, and I was surprised by how poor the built-in DB stuff is. It's like either assembly or Python, but nothing in the middle.

That said I've also been impressed about how nice it is to get stuff going. I used C# back in the .Net 1.1 days and yeah massive difference in ergonomics.

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

#22

Post by LelouBil » Tue, Mar 21, 2023, 10:19 PM UTC

sylens wrote: post #14

cyral wrote: post #12

Been using .NET for years now for backend web development after having taken a break from C#. It is such an improvement over the old .NET framework. When I started building my first backend with it, I was surprised how much was included and "just worked". Need to add authentication? Few lines. OAuth? Also built in. Response caching? Yes. ORM? EF Core is pretty good. Need to use env variables to override your JSON con…

It really is like finding enlightenment after having to figure out which third party package is best for every little thing in Node. Visual Studio is a pretty powerful IDE as well.

Jetbrains Rider is great for .NET too, although I didn't try backend developement with it.

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

#23

Post by pmoriarty » Tue, Mar 21, 2023, 10:19 PM UTC

As a fan of O'Caml, I have to ask: what's the status of F# on .NET?

...and is it used much compared to C#, or is its use at least growing, or is it stagnating/dying?

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

#24

Post by tester756 » Tue, Mar 21, 2023, 10:20 PM UTC

magicalhippo wrote: post #21

cyral wrote: post #12

Been using .NET for years now for backend web development after having taken a break from C#. It is such an improvement over the old .NET framework. When I started building my first backend with it, I was surprised how much was included and "just worked". Need to add authentication? Few lines. OAuth? Also built in. Response caching? Yes. ORM? EF Core is pretty good. Need to use env variables to override your JSON con…

> ORM? EF Core is pretty good. We're moving to .Net, and I was surprised by how poor the built-in DB stuff is. It's like either assembly or Python, but nothing in the middle. That said I've also been impressed about how nice it is to get stuff going. I used C# back in the .Net 1.1 days and yeah massive difference in ergonomics.

>It's like either assembly or Python, but nothing in the middle.

Dapper seems to be in the middle and it is pretty popular

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

#25

Post by doodlesdev » Tue, Mar 21, 2023, 10:22 PM UTC

pyjarrett wrote: post #16

tiffanyh wrote: post #2

It’s a tired thing to say, but the “.NET” naming is so confusing on what’s what. Which is sad because there’s so much to like about .NET

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.

What about Mono and Unity?

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

#26

Post by 0xDEF » Tue, Mar 21, 2023, 10:23 PM UTC

magicalhippo wrote: post #21

cyral wrote: post #12

Been using .NET for years now for backend web development after having taken a break from C#. It is such an improvement over the old .NET framework. When I started building my first backend with it, I was surprised how much was included and "just worked". Need to add authentication? Few lines. OAuth? Also built in. Response caching? Yes. ORM? EF Core is pretty good. Need to use env variables to override your JSON con…

> ORM? EF Core is pretty good. We're moving to .Net, and I was surprised by how poor the built-in DB stuff is. It's like either assembly or Python, but nothing in the middle. That said I've also been impressed about how nice it is to get stuff going. I used C# back in the .Net 1.1 days and yeah massive difference in ergonomics.

>We're moving to .Net, and I was surprised by how poor the built-in DB stuff is

Right now EF Core is probably the best ORM that has ever existed. What exactly is missing?

Although for performance you would probably reach for something like Dapper but that is not an ORM.

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

#27

Post by lp0_on_fire » Tue, Mar 21, 2023, 10:23 PM UTC

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 it will take a massive amount of work to update from dotnet 6 to 8, or 8 to 10 in a few years? Probably not, but that could change at any time depending on the whims of Microsoft on that particular day.

I get that the current technical zeitgeist is that if you’re not releasing a new version every other day you’re falling behind but five years seems a bit more reasonable to me.

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

#28

Post by cyral » Tue, Mar 21, 2023, 10:24 PM UTC

magicalhippo wrote: post #21

cyral wrote: post #12

Been using .NET for years now for backend web development after having taken a break from C#. It is such an improvement over the old .NET framework. When I started building my first backend with it, I was surprised how much was included and "just worked". Need to add authentication? Few lines. OAuth? Also built in. Response caching? Yes. ORM? EF Core is pretty good. Need to use env variables to override your JSON con…

> ORM? EF Core is pretty good. We're moving to .Net, and I was surprised by how poor the built-in DB stuff is. It's like either assembly or Python, but nothing in the middle. That said I've also been impressed about how nice it is to get stuff going. I used C# back in the .Net 1.1 days and yeah massive difference in ergonomics.

EF Core when it first came out was pretty rough but they have been adding a ton, especially in .NET 7 and coming up with 8: https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-cor... Most of the pain points for me are solved now. Like someone else mentioned, Dapper can fill the gaps.

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

#29

Post by alexzeitler » Tue, Mar 21, 2023, 10:24 PM UTC

LelouBil wrote: post #22

sylens wrote: post #14

Earlier quoted context omitted.

It really is like finding enlightenment after having to figure out which third party package is best for every little thing in Node. Visual Studio is a pretty powerful IDE as well.

Jetbrains Rider is great for .NET too, although I didn't try backend developement with it.

I’m using it for backend work day in and day out and it’s a joy.

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

#30

Post by older » Tue, Mar 21, 2023, 10:24 PM UTC

sylens wrote: post #14

cyral wrote: post #12

Been using .NET for years now for backend web development after having taken a break from C#. It is such an improvement over the old .NET framework. When I started building my first backend with it, I was surprised how much was included and "just worked". Need to add authentication? Few lines. OAuth? Also built in. Response caching? Yes. ORM? EF Core is pretty good. Need to use env variables to override your JSON con…

It really is like finding enlightenment after having to figure out which third party package is best for every little thing in Node. Visual Studio is a pretty powerful IDE as well.

Yes, since VS2022 became 64-bit app it is much more pleasant to use now.