|
|
|
|
|
by pjmlp
1738 days ago
|
|
Someone is wrong on the Internet. .NET has always supported AOT via NGEN, although it only supports dynamic linking and was optimized for fast startup of applications. Windows 8 introduced the Bartok compiler used by Singularity, where applications would be pre-AOT compiled in the Windows store minus linking, with on-device linking happening on installation. Windows 10, improved the later scenario with the introduction of .NET Native, slightly based on the Midori experience. The new Windows 11 store is still fully based on .NET Native, as it makes use of WinUI 2.6. |
|
I didn't claim otherwise. But AOT != "native".
What makes something "native" is not merely the fact that you compile to machine code. It's one of the main features of native code but far from the only one. Again: there's a reason they came up with ".NET Native" and called it that despite the fact that NGen always did AOT. And there's a reason the Android NDK has an N, unlike its SDK. It actually means something beyond AOT.
You can go against the grain if you want and call them all native apps, telling people they're Wrong On The Internet, but you're just confusing people.