What is this Blazor thing, anyway?
summary
Explains that WebAssembly is a stack‑based binary VM running in modern browsers, promising near‑native performance for compute‑heavy tasks; toolchain uses LLVM/emscripten and has frontends for C/C++, Rust, Kotlin and .NET via Mono runtime compiled to WebAssembly (Blazor) or Bolero for F#. Notes hard limits: no direct DOM access (must call back to JS) and Blazor currently runs a VM inside a VM, so latency and resource constraints make it not yet a drop‑in replacement for typical web apps, but good for games or audio synthesis.
AI-written summary · about
chapters (11)
- 0:00Introduction to WebAssembly
- 0:45What is WebAssembly?
- 1:50Why do we need it?
- 2:43Past web technology attempts
- 4:20Advantages of WebAssembly
- 6:10Goals and design principles
- 7:27How WebAssembly works
- 8:27Technical example: factorial
- 10:17Tooling and language support
- 11:37Challenges and limitations
- 12:56Conclusion and Q&A
related talks
58mBlazor: C# running in the browser via WebAssembly
01h 01mBlazor: Modern Web development with .NET and WebAssembly
46m.NET: What's Blazor - Front .NET
47mBlazor
09mBlazor with WebAssembly
59mBlazor, a new framework for browser-based .NET apps
01h 03mBlazor, a new framework for browser-based .NET apps
01h 13mBlazor: SPAs in the Browser with C# and WebAssembly
