Blazor
summary
Blazor WebAssembly runs C# in the browser on an interpreter so CPU-heavy work is slower than React/Angular but AOT in .NET 6 promises native WebAssembly hotspots at the cost of larger bundles; lazy-load those modules. Advice: keep proprietary or heavy logic on the server and call APIs. Uses Mediator/CQRS with single-action API endpoints, vertical-slice features, and shared models to avoid duplication. Maintains NuGet packages with 1,000,000 NuGet downloads. Developer pain point: hot reload missing. Book builds one app end-to-end.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 2:59Blazor performance comparison
- 8:59Why choose Blazor
- 16:45Blazor adoption and growth
- 24:10Blazor community support
- 36:08Blazor future outlook
- 39:58Missing Blazor features
- 42:06Blazor in Action book overview
- 47:00Closing remarks
related talks
46m.NET: What's Blazor - Front .NET
36mBlazor - Full Stack Web Development in C# Only
01h 01mBlazor, a new framework for browser-based .NET apps
47mBlazor - Next Generation UI with .NET 6
15mWhat is this Blazor thing, anyway?
01h 01mBlazor, a new framework for browser-based .NET apps
01h 13mBlazor: SPAs in the Browser with C# and WebAssembly
58mIntro to Blazor, WebAssembly and Razor in .Net
