3 ms·

I would, now that Blazor is the flagship Web Framework for .NET which supports multiple render modes and hosting options, inc. in MVC and Razor Pages or as a ge

by mythz 3y ago

I would, now that Blazor is the flagship Web Framework for .NET which supports multiple render modes and hosting options, inc. in MVC and Razor Pages or as a general templating solution (e.g. for rendering Emails). It's going to be the framework with most of the focus that most .NET Developers will eventually move to. Given the mindshare iron grip Microsoft has over .NET ecosystem, it's able to dictate the Web Framework that most of .NET will use - which is now Blazor. But now that Blazor SSR with Enhanced Navigation offers an optimal UX out-of-the-box, Blazor's going to become the only real future option for Web Development in C#/.NET. I wouldn't have considered it (for Internet App's) before .NET 8, but now its basically the only real future choice for creating any kind of new Web App in .NET (excl. CDN Hostable, SSG Websites).

baz00 3y ago
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.
- mythz 3y ago
  > Yeah, um, I was there for Silverlight and Web Forms. 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.
- stanac 3y ago
  I was there for silverlight and web forms as well. Web Forms had to die IMHO, it was unnecessary abstraction for those who didn't want to learn web. Silverlight on the other had was not (in my opinion) killed by MS but by browser vendors. It was the same time when flash and other plugin based tech died because browser vendors didn't want to support browser plugins. 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.
- mvdtnz 3y ago
  Two deprecated technologies in 21 years, are you serious? Their main templating language, Razor, has been around since 2010. Silverlight and Webforms continued to get support for many years after they were superceded.

by mythz 3y ago

baz00 3y ago

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.

mythz 3y ago
> Yeah, um, I was there for Silverlight and Web Forms. 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.
stanac 3y ago
I was there for silverlight and web forms as well. Web Forms had to die IMHO, it was unnecessary abstraction for those who didn't want to learn web. Silverlight on the other had was not (in my opinion) killed by MS but by browser vendors. It was the same time when flash and other plugin based tech died because browser vendors didn't want to support browser plugins. 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.
mvdtnz 3y ago
Two deprecated technologies in 21 years, are you serious? Their main templating language, Razor, has been around since 2010. Silverlight and Webforms continued to get support for many years after they were superceded.