News for hackers. Stuff that matters.
Re:.NET 10 by greener_grass on Wednesday November 12, 2025 @09:57AM (#45901024)
> 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.

Re:.NET 10 by parliament32 on Wednesday November 12, 2025 @12:36PM (#45903072)
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 :)
Re:.NET 10 by orphea on Wednesday November 12, 2025 @03:32PM (#45906163)

  > Create a hello world dotnet container
The container image is 10.9 MiB. The binary is 1.2 MiB.
Re:.NET 10 by mycall on Thursday November 13, 2025 @07:09AM (#45913950)
While that is small for a container and modern binary, I recall C hello worlds being 17KiB -- if only AOT/Spans/interop be used more to drive down those filesizes further.
Re:.NET 10 by M4R5H4LL on Wednesday November 12, 2025 @02:30PM (#45905036)
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.”
Re:.NET 10 by maximilianburke on Wednesday November 12, 2025 @02:25PM (#45904938)
Sounds like a problem with the "proper SaaS microservices model" more than .NET
Re:.NET 10 by hvb2 on Wednesday November 12, 2025 @03:07PM (#45905694)
If you have that many containers, you should be having the revenue to pay for that.