4 ms·

I worry this is close to Web Forms again.

• thomasz 8y ago
  The Problem with Web Forms was that it shoehorned statefull patterns that worked in desktop programming into http and thereby introduced very leaky abstractions. I see absolutely no reason why this should be a problem for frameworks like blazor.
• m_fayer 8y ago
  This is inspired by Vue/Angular. If you're familiar with those and dig into the docs you'll see that it's conceptually very similar. Nothing like Web Forms.
  • aikah 8y ago
    .
    • cm2187 8y ago
      No a server is not mandatory to run blazor. You can run blazor server side, where the client is routing all events to a server. But that's not the way it is designed to work by default. By default everything runs client side, you could run it from a static website.
• pknopf 8y ago
  I agree. WebForms/UpdatePanel was a half-baked solution to pick-up and drop-in .NET developers from WinForms to the web, while Blazor seems to do the same thing for server-side and client-side developers.