Yeah, um, I was there for Silverlight and Web Forms.
Also your last point is quite frankly crack smoking. You can still dump out perfectly good dynamic content with Razor and MVC.
Also your last point is quite frankly crack smoking. You can still dump out perfectly good dynamic content with Razor and MVC.
On the other had MS gave Silverlight 10 years of support when they announced the death of the tech, MS couldn't do anything else about it. If they waited long enough they could have ported silverlight to wasm today. I think there was a company offering dev tools for compiling silverlight to js and wasm, not sure if they are still around.
Silverlight's demise was inevitable along with the death of Flash and WebForms is a 20+ year old technology that was focused on retaining a Desktop App development model for the Web, an inferior abstraction which would have never lasted. Blazor is unlike either and delivers a great UX OOB.
> You can still dump out perfectly good dynamic content with Razor and MVC.
and you always will be, Blazor just has a superior component and development model, an official API for statically rendering components outside a Web Framework context and will eventually be what most of .NET will be using.
Feel free to use whatever makes you happy, we still heavily use Razor Pages + SSG for our (CDN hosted) statically generated websites + docs, but will be predominantly using Blazor for new .NET Web Apps.