The One Reason Why Razor is Dead...

If you love Razor watch this video and leave a comment. Today I discuss why I believe Razor is just about to bite the dust and has been on a long trudge towards its inevitable place with silverlight, IE, and the windows phone.

Leave a like or dislike, let me know how you feel. But if you like this content also let me know that so i can make more.

[zimcoder]

"Razor is dead, but I will still program in it because it makes some money"... :) That's when you realise you have been click-baited and a youtuber is just fulfilling their quota of weekly videos...

[SajadJalilian]

It's 2024 and I prefer Razor Pages + HTMX over Blazor

[guillermomazzari]

I just started this year as a dev, my first language is c#, and my first big project, was an Instagram clone with MVC using razor pages, I managed to work it out with no javascript at all, but yes, it was horrible, I am currently rebuilding the project using an API and VUE for the front, the experience is soooo different, I recently learned about the existence of Blazor, and I'm so looking forward to its growth, I find it awesome, honestly, I don't like javascript's syntax, clunky, unorganized and weird, I would love to become a full-stack with c# and Blazor, hope this comes true soon enough <3

[juliogutierrez]

I ve been struggling so much trying to understand why a simple form post would refresh the whole screen... Until I just realized it is the way Razor Server works. That got me into Ajax and handling those calls client side to update state in the browser avoiding the page reload.
I am a backend developer and did not have much experience with frontend, still I have to say that Razor is very fast and simple for small projects, mostly one pagers, when you understand the core concepts of how it works.

[Jonas-zpep]

Hypermedia baby, Razor Pages with HTMX rocks! 😎

[AGAU]

Quite a few people are now using HTMX with Razor Pages because it fixes the issue you are talking about and now prefer it to using Blazor. Thoughts?

[evilbee]

Also: Blazor is better than React because it has far less (or zero) dependency on Node packages. The amount of time I’ve lost in dependcy hell because of “npm update” failing is mind blowing. I’ve always thought it was stupid to have npm and Nuget in the same assembly…

Also JavaScript was good when people actually used it to script. Then Node came along and made JS do all of the things that PHP used to… I guess people thought JS was better looking than PHP code but when you’re making entire modules out of it inside a .NET solution it just looks a mess

[andersondamasceno]

What do you think about MVC? Actually I am learning MVC and Blazor, the first one because I see a lot of demanding in the c# market.

[nelsonazolukwamprojects]

Compare Razor with Python Django, not JavaScript

[trevordennis]

Razor is dead? I'm still supporting WebForms! At least until I can do a complete re-write of my application in Blazor. Starting with Blazor Server but it's completely hostile to mobile web browsers since they disconnect every time you switch away from the browser. User gets a reload message every time they come back. Wasm is probably the best solution but should be an easy convert afterwards just to replace the services layer if I need it.

[paulsturm]

I started using razor pages last week, and at first i felt i did something wrong, using jQuery and stuff since every possible solution to achieve what i wanted seemed quite ungodly. I understand now that's just the way razor is and will gladly shittalk razor from now on

[amnesia]

I'm happy with Blazor... or better, I love Blazor

[benimfavorilerim]

Bro.. 1st => Thanks, you are doing good job. If Blazor flights, you will be Elvis of this new world.. :)
And 2nd => Do you remember Visual Studio Lightswitch? MS is so talented to give great names to some technologıes and then kill them quietly.. I don't know why, but, Blazor androids me exactly those killed ones.. :( I hope that I am wrong.