The Blazor Competitor is Here!

Hello, everybody. I'm Nick, and in this video, I will introduce you a Blazor alternative called Hydro. It aims to provide a similar experience without using complicated tech behind the scenes.

Don't forget to comment, like and subscribe :)

Social Media:

#csharp #dotnet

[krzysztofjeske]

Hi, Hydro creator here. Thank you Nick for checking out Hydro and creating this video! Thank you everyone who tried Hydro, I'm grateful for the support you gave by starring the repo and testing the features. I really appreciate that. I appreciate also all the comments, positive ones and the criticism - both are needed!

[MAMW]

lmao we're full circle back to webforms and update panels

[JoseLuisOrihuelaConde]

It's a cool idea, but late in time. Blazor 8 give us a lot of choice on how to create components and its render modes. I think that WASM is evolving in an effective way and it's the way to go.

[LiveErrors]

Im getting pretty sick of youtube videos not putting the name of the subject in the title

[SuperWarZoid]

idk, at this point i think i'll stick to blazor

[keyser]

Competition is always good, and I genuinely wish the creator luck! That said, as a business owner & architect looking for a solid production-ready platform that will be supported for years going forward, Blazor still seems like the more obvious choice. I'm not seeing any compelling reasons for me to switch, not yet anyway. If nothing else, maybe this will force MS to address any major limitations in Blazor, and that's a good thing. :)

[Tsunami]

I'm not sure how I feel about Hydro (reminds me of WebForms), but I generally agree that alternatives are a good thing. ...so long as we don't get to JavaScript levels of "framework of the week".

[browny]

Hm, htmx with mvc/razor pages seems simpler

[psyaviah]

For the sake of competition and growing ideas, please make more videos on it. Blazor is still preferred for now, but, competition is needed. I like the fact it at least makes it as easy as Blazor to write code. So I'm excited for that. And, to be honest, Blazor needs competition to keep it fresh. I love Steve's work, but what has been done in .NET 8 and the missing templates we have, is really making people furious and is complicated for people...
Maybe hydro can deliver new takes on stuff, and we they can all steal from each other ;)

[ericblankenburg]

He should have spent his time creating an alternative to Maui.

[bartlomiejuminski]

Blazor WASM is my favorite version of Blazor. Just a SPA website without any unnecessary complexity being added.

[kipchickensout]

I went through WinForms and then WPF but wanted a better way of making good UI, went to MAUI which I found hard and weird to use and not so different from WPF, then skipped Uno but tried Avalonia (because of the good reception online) but the support for intellisense and various components just felt so clunky to me, at some point I noticed Blazor and liked it but I wanted to make regular Desktop applications, didn't want to use Avalonia so I decided to go with Blazor Hybrid in MAUI but MAUI does not support linux for some reason so I finally found Photino, which seems like barely anyone knows of it. I have yet to see how well it works for me

And then there's this one that's new yet again

[marciogoularte]

Another good alternative is to use Htmx with Blazor SSR with a per-component route. There is no library for this, but it does similar behavior

[simonegiuliani]

Hi why are you not looking into HTMX + C#?

[hio]

We have blazor static rendering with enhanced forms or we could just user static rendering and HMTX. This seem to need more bolier plate for the same effect. I can't think of any reason why I would want to use hydro instead of the static rendering options.

[IOSALive]

Nick Chapsas, This is awesome! I subscribed because I want to see more!

[logicalsparrow]

I've been excited about Blazor since it came out but haven't had a business case to use it so my knowledge of it isn't too deep, but the existence of Hydro made me question some of the things I thought I knew about it. I went to read the blog post to find out what the reasons were for building it. The idea that having a WASM version of .NET is overkill seems a bit silly to me since you can specify a CDN for that and it will be cached so it should slow down page loads at most once, and I recall that the assembly file was just a few MB, so it's hardly expensive. The SignalR re-connection issue I thought was mostly solved by a feature added in, I think, .NET Core 3.1. The load balancing and connection exhaustion issues might be the only concerns I had left. Anyway, for cases where a push model isn't needed, this AJAX-centered approach seems like a great idea.

[craigmcinnes]

this looks great, especially for people who were mainly server side, perhaps this will give them the confidence to try a bit more front end stuff

[micoberss]

Why not just use htmx with razor pages ?

[leftjabrighthook]

I played around with Hydro, if you are stuck with Razor Pages its a great alternative to Blazor. I like the fact it does not use Signalr.