3 ms·

There are situations where startup overhead matters, and in those cases dotnet is not a good fit at this moment. But there are a lot of areas where it doesn't m

There are situations where startup overhead matters, and in those cases dotnet is not a good fit at this moment. But there are a lot of areas where it doesn't matter and those are where dotnet and Java are typically used. Running the same code a lot is certainly not cheating, a lot of code where performance really matters is actually doing the same thing over and over. .NET 5 added source generators, which are one part that is necessary to get to a point where ahead of time compilation would be feasible for typical .NET projects. So this is an aspect that Microsoft seems to be looking into now.

MarkSweep 6y ago
Adding on to this, the work done to make .NET linker friendly will also help make it more amenable to AOT. For people who have not been following .NET closely, there is a thing called Blazor that runs in the browser using web assembly. To get the download size down, a linker is used to remove classes and methods that are not being used. You can also use this when deploying other types of apps. https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/configure-linker https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and...