Both "deeper dive into NativeAOT" and "MAUI team's perspective on iOS AOT" sounds good. I am using Avalonia to build an iOS app so both perspectives are valuable.
@cheekychappy1234
Күн бұрын
Regarding building the native libraries. - An episode on building a native library and then calling that from C++ would be awesome.
@manamana5495
Күн бұрын
I would like a deep dive into source generators
@emiraksoy1520
Күн бұрын
Amazing content learned a lot! There are a lot of things that should be considered while publishing AOT. For large projects, It can put you in warning/error resolving loops Thanks for the simple but powerful explanation Eric!
@stefancfefo
Күн бұрын
Nice one! Can't wait for native aot for libraries. That sounds very cool
@flygonfiasco9751
Күн бұрын
Oh nice, excited for this one!
@softshells
20 сағат бұрын
Cool something I’ll practice today!
@LunicLynx
Күн бұрын
This is awesome!
@paicore
Күн бұрын
.NET is getting awesome!😀
@dagobertoSanchez
Күн бұрын
Genial, muchas gracias
@pauljeschke194
Күн бұрын
btw hot tip for magnifying: Win+ESC quites it :)
@JethroBodine1422
Күн бұрын
Good stuff.
@alehkhantsevich113
Күн бұрын
Stupid question maybe, but isn't it possible to implement some sort of flag in csproj for Text.JSON to automatically generate typeInfo classes inferring their usage from code? .NET usually written as strongly as possible, so inference shouldn't be a big problem.
@dtienloi
Күн бұрын
🤩🤩🤩
@sealsharp
Күн бұрын
Oh. so Michal beats every challenge? Hallo Michal Strehovský. I bet you can't make RAII for objects to allow allocation does not cause GC pressure. 😁
@adhamjon6720
Күн бұрын
Does winforms support AOT now?
@metaltyphoon
Күн бұрын
Not sure I agree about “just build on Linux because you would need infrastructure”. In Go or Zig this is trivial, so kinda embarrassing. In rust you add the target and install the infra necessary. Why can’t the dotnet workload cmdline do “setup infrastructure” for AOT scenarios? On Linux and macOS it would setup mingw and on windows it would setup gcc/clang
@LunicLynx
Күн бұрын
Why putting this effort down though? C# (a managed language) is very different from a native language. This translation into native code is absolutely non trivial.
@neonmidnight6264
Күн бұрын
NativeAOT supports cross-architecture compilation. Go case quickly becomes useless the moment you need platform-specific crypto, which is more often than you think, or any other OS-specific dependency. You can target NAOT at linux RIDs from under windows by using PulishAotCross nuget package, which uses Zig's build toolchain under the hood. Otherwise, you must compare this to C, C++ and Rust instead, which C#, as compiled by NativeAOT, is much spiritually closer to. It relies on platform linker, the same one your other systems programming languages use, and with the exception of Zig this is an OS-dependent build process.
@DamianPEdwards
Күн бұрын
Official answer RE .NET native AOT cross-compilation is at learn.microsoft.com/dotnet/core/deploying/native-aot/cross-compile The cost to build out the required feature set and infrastructure to enable this in a way that meets our requirements would be significant and unlikely to be prioritized high enough to warrant the investment.
@tosunabi1664
Күн бұрын
Overkill! So many settings to know about. Is it possible to just analyze the method while coding it and warn if it is not AOT compatible and offer ways to fix it, so that most code we produce can be AOT compatible.
@BahawalTV
Күн бұрын
How about WinForms?
@sealsharp
Күн бұрын
Try it. Enable the analyzer flag true ( called AOT-compatibility analyzers on the website) and see what it says.
@chintu2691994
Күн бұрын
They always forget WinForms like old friends and will eventually be forgotten. I feel bad for all WinForms devs
@sakesun
Күн бұрын
I guess normally libraries use many Reflection. AOT was quite specifically built to address cold-start issue for serverless microservices.
@antoniusivan8767
Күн бұрын
youtuber is afraid to benchmark aspnetcore (native aot). Because their programming language and framework will get beaten so hard. hahaha
@LunicLynx
Күн бұрын
Why are you putting this comment here? They have been very transparent about the goal here. This is a huge accomplishment, and not because of performance. As mentioned in the beginning this has been an effort going on for 2 decades. It is a very complicated thing.
@shanselman
Күн бұрын
Hm?
@ote8458
Күн бұрын
"hahaha huhiu beaten" a no brainer comment without arguments
@q1joe
Күн бұрын
Huh?
@flygonfiasco9751
Күн бұрын
What benchmarks were you looking for? Against other languages/frameworks? I thought they were pretty open about the state of aot in aspnet core, as well as the benefits and disadvantages to using it, at least in comparison to other publishing options
Пікірлер: 32