Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> 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.



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 :)


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.”


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


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.


Sounds like a problem with the "proper SaaS microservices model" more than .NET


If you have that many containers, you should be having the revenue to pay for that.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: