designs

In case you’re interested in a potential successor: https://github.com/dotnet/designs/pull/147

They do! See https://github.com/apple/swift/blob/main/docs/LibraryEvoluti... You can also see an example of what a .NET integration with Swift ABI looks like here: https://github.com/dotnet/designs/blob/main/proposed/swift-i...

On macOS with ARM chips W^X is mandatory also for JIT: https://github.com/dotnet/designs/blob/main/accepted/2021/ru...

Which kind of AOT flavour? NGEN, .NET Native, the pseudo extract zip, the pseudo extract zip with mmap execution,..... https://github.com/dotnet/designs/blob/main/accepted/2020/fo... Even in .NET 6 it is going to be "almost there, wait a bit more for .NET 7 to cover all use cases". https://devblogs.microsoft.com/dotnet/announcing-net-6-previ...

Same! Your Simple Programs proposal in that area is really great: https://github.com/dotnet/designs/pull/213 I am really looking forward to the day when I can use C# for all my scripting needs instead of Bash/Python/PowerShell. We’re getting there.

It got a lot better in .NET Core three when they stopped using Nuget packages for the core framework works. Now building and updating apps based on just the core frameworks no longer installs and restores Nuget packages. This makes it faster, simpler, and takes less space on disk. You probably still will have more Nuget packages in your ASP.NET Core project than a classic .NET Framework project would. Details about the new system: https://github.com/dotnet/designs/blob/main/accepted/2019/ta...

A sore point for me in .NET, given that Anders was on the team, was the lack of proper AOT compilation (NGEN did not really cut it), Delphi style. We had to wait until Windows 8 to properly get it, and still its being rebooted due to the way WinRT went, whereas it could bave been there since v1.0. https://github.com/dotnet/designs/blob/main/accepted/2020/fo...

Well, if you have been following up on blogs, community videos and github issues, most likely by the time .NET 6 comes out, the stack will look like Windows 7 development model never went away and the only improvement was replacing COM with the improvements brought by UWP. With the store sandboxing Win32 apps instead. https://github.com/dotnet/designs/blob/main/accepted/2020/fo... https://github.com/microsoft/ProjectReunion My biggest grip with .NET, since 2001 alphas for MSFT partners, was not being AOT like Delphi (NGEN was never meant for anything other than fast startups).

More information here, https://github.com/dotnet/designs/blob/main/accepted/2020/fo...

Sadly proper AOT (think .NET Native) has been postponed into .NET 6. https://github.com/dotnet/designs/blob/main/accepted/2020/fo...

Kind of, Microsoft seems to trying to fix UWP, while trying to turn .NET into a cross platform runtime that has an eco-system that has been Windows only for the last 20 years. So while they are doing lots of nice performance improvements, there are plenty of business not so happy that their 20 year investments don't run on .NET Core, and if a rewrite is needed (e.g. WCF vs gRPC) then why not just jump into something else. Just see the lengthy roadmap, and the considerations that not everyone was happy with "AOT" (packing everything into an exe that unzips on execution). https://github.com/dotnet/designs/blob/main/accepted/2020/fo... Also check the repositories from Project Reunion, it is pretty much WIP right now.

> So one of the prime dreams of having .net AOT of having an easy way to create a COMPACT self contained native exectuable dies when it hits real code. They are working on improving that: https://github.com/dotnet/designs/blob/master/accepted/2020/...

Yes, it can contain the .NET runtime like a Go executable. You can already (mostly) do this today with .NET Core 3/3.1 (I say "mostly" just because it simply unzips the runtime on first run). I deploy to Linux with everything in a single file and it's been perfect - headache-less deploys. You can read more at https://github.com/dotnet/designs/blob/master/accepted/2020/... and https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-pu.... I haven't had any problems with it at all. The size is a bit bigger, but I don't really care about that and then I can just run it like anything else without worrying about making sure that the .NET runtime is on my deploy system and kept up to date. You can also use the PublishReadyToRun flag to do AOT compilation so that startup times are faster (https://docs.microsoft.com/en-us/dotnet/core/whats