WebAssembly, it's real, it's coming and it's going to take over web development. Well at least, once it's ready.
Then I ran into Steve Sanderson's Blazor. It's an experimental UI framework running .NET in a browser using WebAssembly.
At first I was really excited about it. But then I realized, there are some issues. A co-worker mentioned similarities to SilverLight. Well that wasn't it. SilverLight basically was a "native" browser plugin with some very opinionated features. WebAssembly is neither.
BUT! Blazor suffers from a fundamental flaw. Yes, its sample implementation offers a Single Page Application. That's not really the issue, as it's completely coincidental (and quite useless, as it's not real).
Blazor implements the .NET framework using Mono. That's pretty slick (seriously!). Again, not an issue.
Blazor also seems to focus on the .NET framework. We don't need a framework running in a browser (that's what SilverLight was - it failed). We just need a compiled, type-safe language in a browser. Blazor does some of that with .NET, C#, IL in a WebAssembly. If I could have C# transpiled into a WebAssembly (instead of IL interpreted by WebAssembly code), I'll be a happy camper. Until then, I'll be looking into using C++ for web development. I don't need the .NET runtime! I need superfast, compiled code.