.NET 5: runtimes
summary
Overview of .NET 5 runtime work: prototypes show Mono (LLVM) runtime can replace CoreCLR by swapping two native files and implementing about five native host callbacks, and this runs. Two prototypes exist — one using an LLVM backend for heavy AOT and one using an interpreter-first tier for fast startup — and both converge into tiered compilation with R2R. Measured startup drops from ~4.0s down to ~2.2s when enabling quick-JIT + tier0 and AOT; LLVM gives higher peak perf at cost of compile time and binary size.
AI-written summary · about
chapters (11)
- 0:00Introduction to .NET 5
- 1:10Evolution of .NET runtimes
- 4:00Legacy JIT and R2R in .NET
- 7:48Mono interpreter as tool
- 10:15Layered compilation and optimizations
- 22:57Startup time optimization
- 33:30Customizing the runtime
- 35:17Mono vs CoreCLR comparison
- 41:16New platform support
- 44:50Mono testing and benchmarks
- 55:31Demo and examples
related talks
51m.NET and WebAssembly: Back to the browser?
46mThe Journey to One .NET with .NET 5 / 6
30mand .NET, what’s next?
58mMobius – writing your own .NET runtime running on .NET Core
50mWhy I'm Not Leaving .NET
01h 04mWhat is new in .NET 6 and the future of .NET
44m.NET 11 in depth: Runtime, libraries, and SDK for the AI era
01h 05mFrom 'dotnet run' to 'Hello World!'