←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 2 comments | 11 Nov 25 15:44 UTC | HN request time: 0.213s | source
Show context
jitbit ◴[11 Nov 25 15:48 UTC] No.45888669[source]▶
For us, every .NET upgrade since .NET 5 has gone surprisingly smoothly and reduced CPU/RAM usage by 10–15%.

We were even able to downgrade our cloud servers to smaller instances, literally.

I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.

replies(26): >>45888799 #>>45888804 #>>45889332 #>>45891939 #>>45896032 #>>45898279 #>>45898305 #>>45898358 #>>45898503 #>>45898877 #>>45899062 #>>45899235 #>>45899246 #>>45899326 #>>45899445 #>>45899481 #>>45899858 #>>45900544 #>>45900791 #>>45900829 #>>45903218 #>>45904345 #>>45904435 #>>45905041 #>>45906073 #>>45907122 #
pier25 ◴[12 Nov 25 18:56 UTC] No.45904345[source]▶
> I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma

There are plenty of real issues that are not the enterprise stigma.

I built a backend web api this year with it and C# is fantastic. EF Core is truly one of the best ORMs I've ever used. That said, I regret that decision and won't be using it again for any new projects.

Honestly it looks like Microsoft is distracted and doesn't really know what to do with .NET. Everywhere you look there are tons of half baked projects like Blazor, Identity or Kiota and progress in .NET is super slow. It's probably going to get worse now with all the AI crap.

replies(6): >>45904474 #>>45904483 #>>45905122 #>>45905539 #>>45905817 #>>45906088 #
shortrounddev2 ◴[12 Nov 25 19:02 UTC] No.45904483[source]▶
Just stick with the classic frameworks. Razor works great as does MVC WebAPI
replies(1): >>45904677 #
1. pier25 ◴[12 Nov 25 19:11 UTC] No.45904677[source]▶
I tried Razor. It's mature, has tons of features, and it's very fast. But it only really solves rendering HTML.

You will still need to integrate Vite somehow to use modern CSS, TS, etc. And if you do that, why even use Razor to begin with?

Also, hot reload is garbage. C# will never get close in speed or features to something like Vite.

replies(1): >>45906253 #
2. shortrounddev2 ◴[12 Nov 25 20:36 UTC] No.45906253[source]▶
If youre intent on writing everything on the frontend in javascript then you can just have a frontend app and use webapi MVC on the backend. Personally, in my personal projects, I find I iterate faster if I dont't write any javascript. Every page is just static HTML and any interaction is done via CSS (which you can do perfectly well in razor pages) or html forms. Managing page state is a huge time sink and IMO not worth it, but it's what pays the bills lol