←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 2 comments | 11 Nov 25 15:44 UTC | HN request time: 0s | 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 #
leetharris ◴[11 Nov 25 16:35 UTC] No.45889332[source]▶
> I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.

Too hard to ignore the benefits of cross-stack gains in Typescript/Python. The C# native phone, Blazor, etc just isn't quite there yet. Tried it at the last company, and full stack TS was just so much easier to do.

The reality is that the vast majority of startups don't make it. The #1 thing startups should be focusing on is hiring the right people and product velocity. TS just makes that easier in my experience.

replies(3): >>45890709 #>>45898233 #>>45898434 #
phillipcarter ◴[11 Nov 25 18:06 UTC] No.45890709[source]▶
Is it though? Backends can be any language and there's a lot more variety there -- TS+node, Go, Python, Java. It's just .NET that's largely ignored for no real technical basis.
replies(4): >>45896164 #>>45898627 #>>45898862 #>>45904484 #
1. pier25 ◴[12 Nov 25 19:02 UTC] No.45904484[source]▶
> Backends can be any language

In +90% of cases you will still need a frontend for that backend.

TS full stack is by far the best option for this.

replies(1): >>45906940 #
2. phillipcarter ◴[12 Nov 25 21:24 UTC] No.45906940[source]▶
Not really? Having come deom a TS + Go startup it’s pretty trivial to wire up domain objects across each language and define a clean API boundary with some enforcement at build time. And Go was a far better choice for the backend than TS for some lower-level memory considerations.