Yes, 2 only applies to server-side Blazor. "Server-side Blazor" itself will be renamed[0] to Razor Components so as to disambiguate it with WASM-in-the-browser

Yes, 2 only applies to server-side Blazor. "Server-side Blazor" itself will be renamed[0] to Razor Components so as to disambiguate it with WASM-in-the-browser, which will still be called Blazor. Razor Components seems to be a blend of different kinds of web programming models, as described by the parent poster: - Traditional: POST + Redirect + GET - Single Page App: Thick client in JS - Razor Components: Traditional, but instead of POST+Redirect, it uses Web Sockets to asynchronously update state. Razor Components are being shipped because it's building off well-known, mature technologies. OTOH, Blazor (WASM in browser) is still baking. For example, there is no tree-shaking to minimize the minimize the size of components needed to run your Blazor app. (IIRC, the average size of a basic nav app is ~2MB.) [0]: https://blogs.msdn.microsoft.com/webdev/2018/10/02/blazor-0-6-0-experimental-release-now-available/ https://blogs.msdn.microsoft.com/webdev/2018/10/02/blazor-0-...