I cannot tell you how much I would give to just be able to use c# and the .net framework in the browser. One well documented, well thought out, consistent, backwards compatible, structured framework that I could use on both client and server would be so much more productive for me.
The attraction of Meteor is that if I can’t have that, then at least Meteor gives us most of that, albeit at the cost of having to give up using a strongly typed language.
I’ve said it before, but Microsoft has totally dropped the ball on the rise of the SPA; ASP.NET is still focussed on statically rendered pages with a sprinkling of AJAX, leaving long time .netters like us looking for a holistic solution outside of the Microsoft landscape. .Net people aren’t used to thinking about what linting package to use, we just start coding. ASP.NET is clinging on as a REST endpoint provider via Web API, but once GraphQL takes hold it’s going to be harder and harder to find a reason to keep using ASP.NET at all, at which point you can imagine there will be an exodus.
There’s a massive opportunity for whoever can provide a one-stop solution to building SPAs to those in the .net world looking around for a solution for writing SPAs, you have to give MDG props for seeing that one coming.