←back to thread

.NET 10

(devblogs.microsoft.com)
484 points runesoerensen | 6 comments | 11 Nov 25 15:44 UTC | HN request time: 0.771s | source | bottom
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 #
parliament32 ◴[12 Nov 25 12:46 UTC] No.45899481[source]▶
I think the key problem is that a large number of startups are shipping software in containers, and dotnet requiring a CLR is not particularly well-suited for containerization. It's like the old school Java JVM model. You have to ship a copy of the runtime with every container, and if you're doing proper microservices it's an awful lot of overhead.

Yes I'm aware MS makes it easy to build containers and even single executables, but languages that compile down to an ELF are pretty much a requirement once your deployments are over the 10k containers mark.

replies(11): >>45899527 #>>45900963 #>>45901005 #>>45901024 #>>45901026 #>>45901133 #>>45901711 #>>45901752 #>>45903133 #>>45904968 #>>45905736 #
1. greener_grass ◴[12 Nov 25 14:57 UTC] No.45901024[source]▶
> dotnet requiring a CLR is not particularly well-suited for containerization

Why? I routinely put compiled .NET programs into containers.

It's also easy (easier than Rust even) to build on Mac targeting a Linux image.

replies(1): >>45903072 #
2. parliament32 ◴[12 Nov 25 17:36 UTC] No.45903072[source]▶
Create a hello world dotnet container, then do the same in a modern language. Then compare image size and resource consumption. Then imagine you're running tens of thousands of containers in a proper SaaS microservices model, and it'll make sense :)
replies(4): >>45904938 #>>45905036 #>>45905694 #>>45906163 #
3. maximilianburke ◴[12 Nov 25 19:25 UTC] No.45904938[source]▶
Sounds like a problem with the "proper SaaS microservices model" more than .NET
4. M4R5H4LL ◴[12 Nov 25 19:30 UTC] No.45905036[source]▶
Enterprise doesn’t spawn 10,000 containers to perform a simple “hello world” operation. That’s not how it operates. You’d be amazed at how many concurrent requests a single service can handle. This capacity must align with the actual requirements of the companies involved, not some unrealistic scenario like “we need to emulate Google.”
5. hvb2 ◴[12 Nov 25 20:07 UTC] No.45905694[source]▶
If you have that many containers, you should be having the revenue to pay for that.
6. orphea ◴[12 Nov 25 20:32 UTC] No.45906163[source]▶

  > Create a hello world dotnet container
The container image is 10.9 MiB. The binary is 1.2 MiB.