My take on it was that with Blazer, you can make client side apps sort of like Angular, in which you can type your client side code in c# instead of JavaScript or TypeScript, and a Blazer utility sort of like Babel will translate your c# code into current and backwards compatible JavaScript, and automatically insert it into the server side generated HTML, and transmit it back to the client. This reminds of .Net MVC, in which you can add React client and server via NuGet packages, and write react modules to insert on Razor pages, in which Babel will translate the React module into JavaScript and integrate into the server generated HTML and send the page to the client. So instead of client generating React JavaScript, it's done on the server side, so that .Net can keep track of it. Babel is a translator, that can generate backwards compatible JavaScript from ECMAScript 2015+ [What is Babel? · Babel](https://babeljs.io/docs/en/) So in my mind from what I read of it, Blazer is sort of like ReactJS using Babel, or AngularJS in which you can create a single page application SPA within a single Razor page all in c# without the steep learning curve of ReactJS or AngularJS.
If it ain't broke don't fix it Discover my world at jkirkerx.com