.NET and WebAssembly: Back to the browser?
summary
Mono runtime compiles to WebAssembly so a full .NET Standard 2.1 runtime runs in browsers by compiling the runtime with LLVM/Emscripten, using an interpreter plus optional AOT-compiled methods and an IL linker to trim size. Blazor and Uno demos run real apps (Windows Calculator port). Networking is browser-limited, threading via SharedArrayBuffer is experimental, GC is cooperative, and debugging uses a proxy to Chrome DevTools. Tooling shows Mono runtime compiled to WebAssembly, mixed AOT + interpreter reduces size, 30% startup speedup with simple profiling.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 0:52Browsers
- 1:46Other attempts
- 3:05WebAssembly
- 4:29WebAssembly Binary
- 5:34WebAssembly Structure
- 8:34WebAssembly Types
- 9:20Sample Instructions
- 9:47The Problem
- 10:44The Solution
- 13:55LLVM
- 14:39Scripting
- 15:21Abstract
- 15:52Blaser
- 16:52No Platform
- 18:06buoy
- 18:49big problems
- 20:12speed
- 22:09interpreter mode
- 25:02linker
- 27:40size comparisons
- 27:55CI builds
- 28:23Tree maps
- 33:48Networking
- 35:31Threading
- 37:14Garbage Collection
- 38:52Debugging
- 42:28Chrome Debugger
- 44:57Testing
- 45:45WebAssembly Work
- 47:01Cindy
related talks
58mBlazor: C# running in the browser via WebAssembly
43mWebAssembly & .NET: The Future of Cross-Platform Apps
29mBringing WebAssembly to the .NET Mainstream
01h 01mBlazor: Modern Web development with .NET and WebAssembly
59mBlazor, a new framework for browser-based .NET apps
41mBlazor, a New .NET Single Page Application Framework
09mBlazor with WebAssembly
52mWebAssembly and the future of the web platform