What is Blazor? What is it used for? What kind of applications can you write with it? Is it client side or server side? This free crash course on building Blazor WebAssembly applications based on .NET 5.offers a first class opportunity to get behind the hype of what Blazor is and what it can do.
Blazor is a way to write web applications both on the server and client side with .NET and C# instead of using Javascript on the front-end. If you've heard of the Vaadin framework then Blazor is something similar. But with a small difference...code in Blazor compiles to WebAssembly, not Javascript. The way it works is that a .Net runtime compiled to WebAssembly is downloaded into the user's browser which then runs the Blazor application in the same sandbox that Javascript runs. And due to this magic of WASM, you can run high intensity apps, even C++ games, inside the browser!
But doesn't it sound just like a Java Applet? An Applet needs a browser plugin and a host machine running JVM. In contrast WASM is targeting the browser's engine, for instance Chrome's V8. Additionally it can still interoperate with Javascript, especially since it currently can't access the DOM directly. That's one reason that it is branded as not a replacement to Javascript but as complementary to it.