4 ms·
Which kind of proves the point I made elsewhere about ASP.NET Ajax, as Blazor in spirit is a kind of WebForms 2.0/Silverlight.
by pjmlp 3mo ago
Which kind of proves the point I made elsewhere about ASP.NET Ajax, as Blazor in spirit is a kind of WebForms 2.0/Silverlight.
- gwbas1c 3mo agoHonestly, I didn't do much with webforms other than a "Hello World" project. I hated it; fortunately at the time my paid gig was Winforms. (C# Desktop.) Webforms just hid too much of "the web" to be useful, IMO. Silverlight required a proprietary browser plugin. I wouldn't touch it with a 10-foot pole. Blazor (server-side) doesn't hide the web; although if you need to do things that are "close to the wire"; you should either use the WASM variant or a different stack. Remember, I use server-side Blazor for things that would be ad-hoc queries or scripts, and it's for a website that only a handful of employees use. I'm not sure how it would handle an "industrial strength" massively-scalable application. (At least in that situation, most of the code will port nicely to WASM so you do have an exit strategy that doesn't require a whole rewrite.)