3 ms·
Some very nice improvements! I hope that this trend with focus on performance continues in the future and that NativeAOT becomes first class citizen soon.
by zigzag312 5y ago
Some very nice improvements! I hope that this trend with focus on performance continues in the future and that NativeAOT becomes first class citizen soon.
- pjmlp 5y agoBecomes again, Native AOT is the only way on WinRT since Windows 8, but has been stuck in C# 7 and .NET Standard 2.0, which contributes even more for the little love UWP still has.
- ComputerGuru 5y agoNot just stuck - it was buggy and poorly maintained. We were forced to switch to Desktop Bridge after dealing with all the UWP performance and productivity crap and constraints just to have .NET Native one day stop compiling things right and leaving us stuck.
- tasogare 5y agoUWP was doomed to fail from day 1 because of how it was tight to UI framework and distribution model. Having a separate, incompatible implementation of the .net framework was another big smell.
- jeswin 5y agoIf I remember correctly, WinRT doesn't use Native AOT. Native AOT has never been released before, and to me is the most exciting feature since generics in .Net 2.0 (circa 2005).
- ripley12 5y agoIt will be interesting to see how well trimming and AOT (closely related technologies) turn out. I’ve already been able to build useful trimmed self-contained CLI apps with .NET 5 and 6, and based on what I’ve seen of NativeAOT I think it’d work for those. OTOH things get dicier the further you get away from the core .NET libraries, and some of the enabling technologies are so new that they haven’t seen much adoption yet (example: the venerable COM interop system vs the new ComWrappers). If you’d like to keep up to date on NativeAOT, Andrey Kurdyumov is doing some top-notch work in the area: https://codevision.medium.com/ https://codevision.medium.com/