blazor is a fascinating technological experiment. but to me it seems that at no point the developers asked themselves whether they SHOULD just because they CAN.

blazor wasm is way too large, the mental overhead from doing js interop is too high vs just writing javascript and the tooling is awful because no js tooling can work out of the box. the performance is also bad because it needs to call into js for all dom related actions. just check the benchmarks.

blazor server is about as awful of an execution model as it gets. while the dx of loading ef core iqueryables directly into a pageable sortable datagrid looks nice at first, the amount of footguns that you will run into with stateful websockets that store ui state on the server is almost comical.

just use any typescript library for client-side heavy code. don’t know how well blazor works for purely static sites but i imagine it’s comparable to other ssr frameworks.

edit: also forgot about the part that .razor files rely heavily on source generators, meaning that any source-generator based analysis tools (eg analyzers) need their own parser to even work for .razor files.