Goodbye client side JavaScript, Hello C#'s Blazor

on YouTube ↗36m

" summary

Blazor claims to let C# run in the browser by compiling the .NET runtime to WebAssembly and shipping DLLs to the client so browser code executes on Mono; the client build currently ships ~2.4 MB of DLLs while the server model sends <0.5 MB and uses SignalR and binary diffs for UI updates. Demos include the counter and fetch-data components, a GitHub Pages–hosted WebAssembly app, and a server-side app using ML.NET, Cosmos DB and SQLite with only tiny JavaScript shims.

AI-written summary · about

" chapters (13)

1. 0:00Start
2. 0:48Previous Attempts
3. 2:45Key Differences
4. 4:50Blazor: Client & Server
5. 5:13How Client-Side Works
6. 7:11How Server-Side Works
7. 8:23At a Glance
8. 10:55Components
9. 12:04Routing
10. 12:26Dependency Injection
11. 12:52Prerequisites
12. 13:27File new Project
13. 35:16Resources

" related talks

• 58mBlazor: C# running in the browser via WebAssemblyScott Sauber · NDC Minnesota 2019
• 01h 01mBlazor: Modern Web development with .NET and WebAssemblyDaniel Roth · .NET Conf 2018
• 41mBlazor, a New .NET Single Page Application FrameworkSteve Sanderson · Øredev 2018
• 56mASP.NET Blazor—the C# Angular or the return of Silverlight?Dino Esposito · .NET Fest 2018
• 01h 03mBlazor, a new framework for browser-based .NET appsSteve Sanderson · NDC Minnesota 2018
• 59mBlazor, a new framework for browser-based .NET appsSteve Sanderson · NDC Oslo 2019
• 51mComponent-based C# and Razor Programming in BlazorDino Esposito · Riga Dev Days 2019
• 59mThe future of Web: what Microsoft Blazor can do for youAlexandre Malavasi · .NET Fest 2019