I believe if you have no other apps interfacing the REST endpoints apart from the blazor app, then you may ignore it. If you also need to effectively scale the individual apps (blazor and REST), consider separating them, IMO.
I'm sure that is a driver, but for natively running app in one executable with native characteristics has been a long top requested feature and they have actually been evolving and experimenting wuth it for many years (in the background)
Indeed, aforementioned scenarios are all enabled by AOT. Things will only improve with time and I'm happy to have chosen .NET 20 years ago. If you remember... There was the promise of a cpu executing MSIL natively... I wonder if one can still find that article. What I did here was to highlight one of the most important reasons which was not mentioned during the stream. Cheers!
Listening to David and Damian is always a treat. Thank you!!
Please make Blazor, MAUI, Minimal APIs and Azure Functions Isolated fully native AOT compliant.
I am in the process of transitioning a sizable project from MVC, which heavily uses REST. Should I reconsider using REST when shifting to Blazor?
I believe if you have no other apps interfacing the REST endpoints apart from the blazor app, then you may ignore it. If you also need to effectively scale the individual apps (blazor and REST), consider separating them, IMO.
Wich is the best architecture for security using blazor? I want to evolve from mvc
Q: Why investing in AOT? A: Because WebAssembly!
I'm sure that is a driver, but for natively running app in one executable with native characteristics has been a long top requested feature and they have actually been evolving and experimenting wuth it for many years (in the background)
You also need AOT for iOS, since it prohibits JIT compiled apps. It may also be the case for Android.
Indeed, aforementioned scenarios are all enabled by AOT. Things will only improve with time and I'm happy to have chosen .NET 20 years ago.
If you remember... There was the promise of a cpu executing MSIL natively... I wonder if one can still find that article.
What I did here was to highlight one of the most important reasons which was not mentioned during the stream.
Cheers!
@@scosminv There's a processor called JOP that's capable of running Java byte codes, but it's experimental.