What you fail to mention is how web assembly allows for web native apps that can run offline. This is massive. It is the reason I chose blazor wasm for the low-code framework I am building to provide the web target. The ability to share existing C# code for the web target, and have it run on the client, is priceless. This is not an intellectual debate - in the real battleground of producing real systems that people really will use daily blazor is a game changer, and given wasm is an open standard is one that will not die the same death as silverlight.