3 ms·

Excited about the smaller standalone binary (native AoT) .NET 8 can generate to compete with the likes of Go

by leeman2016 3y ago

anotherhue 3y ago
Better than go, more like Graal
- geodel 3y ago
  How is Graal better. Half of the Java ecosystem wouldn't work with Graal.
  - svick 3y ago
    Half of the .Net ecosystem doesn't work with AOT either.
    - Smaug123 3y ago
      (Corrective upvote from me. Pretty much any use of reflection dooms you, and reflection is very common.)
  - pjmlp 3y ago
    Just like with Native AOT, as it only supports CLI, dynamic libraries with C ABI, and a special flavour of ASP.NET with minimal APIs introduced now in .NET 8. Mono AOT supports a bit more, with focus on iOS and Android workloads. None of them work with GUI frameworks or classical ASP.NET applications.
    - neonsunset 3y ago
      MAUI iOS can also be targeted by NativeAOT[0] and Avalonia has been proven to work with it as well. Also, you can statically link NativeAOT libraries into existing C/C++/Rust/etc. code, and you can statically link existing static libraries into NativeAOT binaries[1]. [0] https://devblogs.microsoft.com/dotnet/dotnet-8-performance-improvements-in-dotnet-maui/#nativeaot-on-ios https://devblogs.microsoft.com/dotnet/dotnet-8-performance-i... [1] https://github.com/lixinyang123/AvaloniaAOT https://github.com/lixinyang123/AvaloniaAOT [2] https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/interop#linking https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...
      - pjmlp 3y ago
        MAUI iOS with NativeAOT is experimental, and is still only of target out of many. Avalonia is great, however the biggest issue is with Microsoft own tech, as many of us are well aware, many companies are Microsoft shops and only care about what is in the Visual Studio box. There, not only is Native AOT behind .NET Native, there is no plan to ever support AOT in Forms and WPF projects. On the libraries I stand corrected regarding static linking.

Excited about the smaller standalone binary (native AoT) .NET 8 can generate to compete with the likes of Go

anotherhue 3y ago

Better than go, more like Graal

geodel 3y ago
How is Graal better. Half of the Java ecosystem wouldn't work with Graal.
- svick 3y ago
  Half of the .Net ecosystem doesn't work with AOT either.
  - Smaug123 3y ago
    (Corrective upvote from me. Pretty much any use of reflection dooms you, and reflection is very common.)
- pjmlp 3y ago
  Just like with Native AOT, as it only supports CLI, dynamic libraries with C ABI, and a special flavour of ASP.NET with minimal APIs introduced now in .NET 8. Mono AOT supports a bit more, with focus on iOS and Android workloads. None of them work with GUI frameworks or classical ASP.NET applications.
  - neonsunset 3y ago
    MAUI iOS can also be targeted by NativeAOT[0] and Avalonia has been proven to work with it as well. Also, you can statically link NativeAOT libraries into existing C/C++/Rust/etc. code, and you can statically link existing static libraries into NativeAOT binaries[1]. [0] https://devblogs.microsoft.com/dotnet/dotnet-8-performance-improvements-in-dotnet-maui/#nativeaot-on-ios https://devblogs.microsoft.com/dotnet/dotnet-8-performance-i... [1] https://github.com/lixinyang123/AvaloniaAOT https://github.com/lixinyang123/AvaloniaAOT [2] https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/interop#linking https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...
    - pjmlp 3y ago
      MAUI iOS with NativeAOT is experimental, and is still only of target out of many. Avalonia is great, however the biggest issue is with Microsoft own tech, as many of us are well aware, many companies are Microsoft shops and only care about what is in the Visual Studio box. There, not only is Native AOT behind .NET Native, there is no plan to ever support AOT in Forms and WPF projects. On the libraries I stand corrected regarding static linking.