zlacker

>>ig0r0+(OP)
Great news for everyone bar startups competing with them as it looks like Microsoft is turning their multi-billion acquisition of GitHub into a loss leader to get as many devs using their platform as possible, no doubt to flex seamless integrations into Azure which looks like they're executing exceptionally well with their acquisitions & new feature giveaways.

From the side-lines it looks like they're slowly becoming an unstoppable dominant force, what's surprising to me is AWS's / GCP's inaction, they're either asleep at the wheel or they don't see Microsoft's dev mindshare grab as a threat.

>>mythz+S4
Blazor is slow to start but I think long-term will be a game changer.

>>trough+je
You mean Microsoft's latest attempt at Web Forms/Silverlight, a product that yet again tries to muddy the separation between client and server execution contexts using magic.

Seems like every generation re-invents this idea, and every time it fails for the same fatal flaw: Illusions are just that, and you'll wind up hacking around the illusion if you want to do something not envisioned (or run into a bug in the secret sauce).

And before someone replies "it is nothing like Web Forms!!!" here's a direct quote from Blazor's homepage:

> Blazor can run your client logic on the server. Client UI events are sent back to the server using SignalR - a real-time messaging framework. Once execution completes, the required UI changes are sent to the client and merged into the DOM.

That's literally how Web Forms worked.

>>Someon+6g
There's nothing magic about it. Web Forms was a great innovation and brought the WinForms model to the web. It was more productive than anything else at the time and directly influenced MVC patterns (which asp.net itself went towards) and component-based UI.

Blazor is the next evolution in client-side and offers an alternative to building component UI with C# running through WebAssembly instead of Javascript. Again it's much more productive and lets backend teams reuse much of the same code, similar to JS/node projects today.

Blazor's server-side runtime is a optional model where all the component logic can run on the server and be delivered over a SignalR connection to further increase productivity and efficiency where it makes sense (highly constrained devices, local intranet apps, etc. There's even experimental projects to bring Blazor for mobile apps.