↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

How Blazor Is Going to Change Web Development

Blazor is presented as a Microsoft framework for building interactive client-side web UIs with C# instead of JavaScript. The page compares it with older server-rendered applications and with Single Page Applications, then outlines the two Blazor models and what each one is for.

Reading notes
#

  • Blazor lets developers build interactive web UIs with C#, HTML, and CSS, and share code and libraries between client and server.
  • The older web model relied on server-side frameworks such as ASP.NET and PHP to generate HTML for the browser, with most logic handled on the server.
  • That older model is described as having drawbacks like server software requirements, most processing on the server, and slow page loads.
  • Modern SPA frameworks such as Angular, React, and Vue move more logic into JavaScript running in the browser.
  • Blazor Web Assembly compiles files and sends them to the browser, where JavaScript, HTML, and C# run in a sandbox with a version of the .NET runtime.
  • Web Assembly applications can run offline, use static file servers, reuse .NET components, and use Microsoft tooling and debugging.
  • The downsides listed for Blazor Web Assembly are the download of runtime files, browser limits, local exposure of secrets, and incomplete .NET Framework compatibility.
  • Blazor Server keeps the .NET Core server in charge and sends HTML and JavaScript to the browser as a client.
  • The Server model is described as suited to thin clients, with full .NET power and smaller downloads, but no offline use and possible latency from network traffic.
  • The article says to choose Web Assembly for offline, client-side apps served from a static server, and Server for thin-client apps that need the full power of .NET.
  • It argues that Blazor opens up opportunities for rich interactive apps and lets C# developers do front-end work in the language they already know.