Lead Product Evangelist @Kentico, Founding partner @craftbrewingbiz. love to learn / teach web dev & software engineering, collecting vinyl records, mowing my lawn, craft 🍺
Blazer is awesome and glad it's brought a client side option to C# developers (F# devs have had some options for awhile with Fable).
I wish that the focus on Blazer didn't pull so much attention away from classic server side HTML generation with Razor. I feel like Tag Helpers and View Components won't get many enhancements now that everything is pushing Blazor as the solution.
The ASPNET team looks to the community for direction and the community is hyped on Blazor 🤷♂️
2x Microsoft MVP, Google Developer Expert, and Twilio Champion who works in DevRel at Microsoft. International speaker, blogger, open source contributor, and approachable developer community advocate.
Location
Milwaukee, WI
Education
Bachelor of Science, Computer Information Systems - Engineering
This is an interesting observation. At the end of the day, the Razor view engine is shared - yes, that is true. But the way I see it, improvements made to it for Blazor will also be applied to other use cases where it is prevalent.
Lead Product Evangelist @Kentico, Founding partner @craftbrewingbiz. love to learn / teach web dev & software engineering, collecting vinyl records, mowing my lawn, craft 🍺
I would love for the Blazor component model and server-side rendering process to made available for traditional server-rendered HTML.
Web Forms did a lot of things that needed corrected once the web became a more robust platform, but it did have a really rich component model which MVC never got.
I feel like Tag Helpers and View Components could be expanded to do things like content projection and better composition. Since Blazor's rich component model already has these, it would be really cool to see them made available to apps that don't intend to ship all the Blazor bits to the browser.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Blazer is awesome and glad it's brought a client side option to C# developers (F# devs have had some options for awhile with Fable).
I wish that the focus on Blazer didn't pull so much attention away from classic server side HTML generation with Razor. I feel like Tag Helpers and View Components won't get many enhancements now that everything is pushing Blazor as the solution.
The ASPNET team looks to the community for direction and the community is hyped on Blazor 🤷♂️
This is an interesting observation. At the end of the day, the Razor view engine is shared - yes, that is true. But the way I see it, improvements made to it for Blazor will also be applied to other use cases where it is prevalent.
I would love for the Blazor component model and server-side rendering process to made available for traditional server-rendered HTML.
Web Forms did a lot of things that needed corrected once the web became a more robust platform, but it did have a really rich component model which MVC never got.
I feel like Tag Helpers and View Components could be expanded to do things like content projection and better composition. Since Blazor's rich component model already has these, it would be really cool to see them made available to apps that don't intend to ship all the Blazor bits to the browser.