WebAssembly and Blazor: A decades old problem solved

Click for: original source

In mid-April 2019, Microsoft gently nudged a young framework from the “anything is possible” experimental phase to a “we’re committed to making this happen” preview. The framework, named Blazor because it runs in the browser and leverages a templating system or “view engine” called Razor, enables the scenario .NET developers almost gave up on. By Jeremy Likness, Cloud Advocate for Azure @Microsoft.

WebAssembly is a new client-side technology that enables near-native performance without plug-ins in all modern browsers, including mobile. WebAssembly, a binary instruction format for a stack-based virtual machine. WebAssembly provides a portable compile target (called Wasm, for short).

Many languages, including C, C#, Go, and Rust, can compile code that targets the stack-based WebAssembly virtual machine.

Blazor is a client-side library that uses .NET on WebAssembly to support Single Page Applications written in C# using Razor templates.

The article main sections:

  • The Silverlight hope
  • JavaScript as a platform
  • WebAssembly: a new hope
  • The Browser and Razor View Engine
  • C# in the Browser (with dependency injection)
  • Reusable components

… and more. You will fined detailed explanation how Blazor works in a browser. Also plenty of links to further reading. Very exciting!

[Read More]

Tags web-development frontend javascript json browsers performance