I know Microsoft didn’t get this right with naming and you got caught in the trap but there are 2 (actually 3) ways of hosting Blazor.

I also see that this confusion won’t help OP choose Blazor over some more coherent dev environment hehehehe

You are talking about Blazor webassembly, I am talking about Blazor server side, which loads as fast as a “normal” website.

Server side Blazor has other caveats, that’s why I specified it is an intranet project, where server side Blazor fits very well. Anyway, at the moment, Microsoft is still putting effort in polishing both type of Blazor hosting model.

This is not our first Blazor intranet web app and some of them are running in production for one year more or less.

It is really a joy to program using Blazor, especially if you need cross tab/browsers/device/user real time communication, which comes almost free thanks to underlying SignalR channel.

My two cents: I strongly agree with this. We just deployed an intranet blazor server app running on Linux (don’t know which distro) and apache (we might switch to nginx soon). It works very well and we had to write less than 100 lines of JS (mostly for file download and upload) One of my workmates was hired one year ago and at the time he didn’t know anything about .Net stack. Now he is mostly autonomous and he loves .Net and blazor in particular. Obviously YMMV.

Hope devs eat speed module lvl 3 for breakfast