How does a single metric from a highly specialized runtime environment indicate a tech stack is dead? There are things you can do right now [1] to mitigate the

How does a single metric from a highly specialized runtime environment indicate a tech stack is dead? There are things you can do right now [1] to mitigate these cold start issues. Going forward, ahead-of-time compilation will be an option. [2] Aside from cold starts, note that the improvements in .NET make ASP.NET Core one of the fastest web frameworks. [3] The article: > “.Net has almost the same performance as Golang and Rust, but only after 1k iterations(after JIT).” Additions like async/await and nullable reference types make it easier to write bug-free code, which for a lot of folks is a better trade off than “speaking to the hardware directly”. .NET also runs natively on a bunch of platforms now, including ARM. I’d call all of that continuous improvement. Perhaps even reinvention? [1] https://docs.microsoft.com/en-us/dotnet/core/deploying/ready-to-run https://docs.microsoft.com/en-us/dotnet/core/deploying/ready... [2] https://github.com/dotnet/runtimelab/tree/feature/NativeAOT https://github.com/dotnet/runtimelab/tree/feature/NativeAOT [3] https://www.techempower.com/benchmarks/#section=test&runid=57b25c85-082a-4013-b572-b0939006eaff&hw=ph&test=composite&a=2 https://www.techempower.com/benchmarks/#section=test&runid=5...