Blazor is a way to run native code in your browser. Uno is a way to run UWP code as a cross-platform app.

It's slightly more complicated now that we also have Blazor Hybrid: https://devblogs.microsoft.com/dotnet/hybrid-blazor-apps-in-....

Blazor is two things at the moment:

- Blazor Webassembly: C# + .Net runtime + Razor components, all of this compiled to web assembly, running on the browser as a Single Page Application

- Blazor Server: C# + .Net runtime on the server, + a SignalR (i.e: socket.io alternative) connection between the server, + Razor components (rendered server-side, diff are sent to the client to update the DOM)

But that's not all! To make it even more complicated, Blazor Hybrid (or .Net MAUI BLazor? Names I've seen aren't consistent) has been announced: a .Net MAUI application + an embedded web view + a local interop channel!

I really hate how Blazor grew into yet another GUI stack war at Microsoft.

It appears everyone is competing for the GUI stack to rule them all, while appearing to be good old friends to the outside.

Complete lack of direction and vision, for sure