I like the benefits of Blazor, especially the potential of reducing server side processing.
I do caution over investing in the Microsoft technology stack. Microsoft does a few things very well (i.e. IDE's, SqlServer, .Net Core), but increasingly I am finding others doing things better and simpler with faster production turn around times.

i beleive microsoft is getting there with the .net core framework architecture.

I'm finding a lot of my peers at work are skeptical of Blazor. I suspect that it's because in the past things that tried to emulate Javascript but in a different language ended badly (see: RJS) or were just trying to make Javascript more appealing instead of focusing on learning Javascript properly (see: Coffeescript). It sounds like a neat idea to me, and seeing that WebForms won't be coming to .NET 5 is interesting as my job still heavily uses WebForms (and sees no compelling reason to move away from it).

I'll certainly need to investigate Blazor more; it seems like the concept finally was gotten right.

Blazor somehow strongly reminds me of Silverlight, back in 2012 or so. MS also said that this is the way to go for web apps, and nobody should use Javascript anymore. And only 2 years later, MS abandoned it altogether. I know some companies who lost millions of $ because of this, having to reimplement mayor projects with another technology AGAIN. Is Blazor going to be another Silverlight?

What is the point of NOT using a popular SPA framework such as Angular or React anyway? After all, I think that every reasonably fit developer can learn those frameworks in a few days or weeks, if he currently has a C# / ASP.NET background and knows the basics of html/css.

No I don't think that Blazor will be anything like Silverlight. Silverlight (and Flash) died because it wasn't where the Web Standards were/are going, it also relied on extension, and didn't run C# natively in the browser like Blazor (which posed security concerns), however Blazor runs in the same sandbox as Javascript and has same amount of rights.which solves the security concerns and it also embraces Web Standards as it is based on WebAssembly (which is a W3C Standard). You can still use popular SPAs but then you'd be loosing the mature .Net ecosystem, which you get with Blazor as you can load any nuget packages and dlls in the browser and leverage .Net Core's already established ecosystem (and not to mention you can write almost all the code from back to front in C#, which is just awesome).

well said TheBinaryGuy

That's my reason too. I get JavaScript is clunky, but it's ubiquitous. How is this different than the people who say you don't need to learn SQL because you can use an ORM to do SQL for you? I rarely see folks advocating that now; usually it's the acceptance that you should know SQL to optimize your queries rather than just rely on EF or whatever tool. This seems like the same thing, as cool as it looks: Oh you don't need JavaScript because you can write everything in C#.

I thought we *didn't* want one language to rule them all, but use the right tool for the job?

Wayne, Blazor can not be compared with EF for SQL alternative. Blazor is using the open web standard web assembly without any plugin. As a matter of fact, we can use any language to write the front end development now that compiles into web assembly. so, why not we use C# which we are already good at it. Honestly, most .net developers who are in the enterprise industry used javascript mainly for client side validation only. when javascript suddenly becomes main stream language for everything, its difficult accept that fact. If javascript was originally started like typescript, everybody would have loved it. To me, blazor is a very good effort from microsoft and all .net community members should support it. I am not against javascript however i am not javascript guy. :)

Because Web Forms are going away, you suggested to move to Angular, React etc. what about ASP.NET MVC stack?

You can still use Asp.net Core MVC or the new Razor Pages introduced in .Net Core 2.0. I have updated this info on blog post.