2 ms·
I use Blazor day to day. It’s really awesome. You are trading off ease of development for a potentially laggy UI connection, since each UI action re renders acr
by elamje 6y ago
I use Blazor day to day. It’s really awesome. You are trading off ease of development for a potentially laggy UI connection, since each UI action re renders across the wire.
I see it being used heavily for enterprises that know C#, don’t care to learn the latest JS framework, and just want to make a SPA quickly and cheaply.
WASM or client side blazor is definitely interesting, though the client must download the whole .net core runtime when they visit your site.
Open to any questions about Blazor! Big fan of Elixir, but haven’t used LiveView yet.
- mycall 6y agoWhat % do you see Blazor eating React's lunch?
- wenc 6y agoBlazor (client-side) is definitely interesting technology if it ever gets uptake. I can just imagine the performance of a desktop app on the browser (via WASM) without having to fiddle around with JS, front-end frameworks, event models etc. and just write software as if they were targeted towards the desktop. Software development would get easier again and it would be possible for more people to write desktop-class software for the browser. I'm thinking a lot of engineering/technical software that were previously not feasible on a browser could be rewritten for the browser.