True, I’m talking about Blazor WebAssembly, but I’m actually less positive about Blazor server. Although Microsoft’s “advertised” performance for Blazor server is good, I’ve heard some negative real-world feedback about scaling. And the idea of sessions maintained in memory on the server is… not great. If you’re load balancing multiple servers, you need sticky sessions, which is awkward. If you need to do server maintenance, you are basically going to end everyone’s session. And forget using this design with a cloud hosting model. So in my (somewhat subjective) opinion, I’d rather pay the startup tax than go back to a world with in-memory server sessions for every client.