News for hackers. Stuff that matters.

A comment on Blazor – Build client web apps with C#. Parent comment

Re:Blazor – Build client web apps with C# by JamesSwift on Wednesday October 02, 2019 @11:04AM (#21137213)
I went to a meetup focusing on Blazor recently and was really surprised when I found out that Blazor is not "run C# in a browser using WASM" like I thought, but was instead "use your browser as a thin client to C# on the backend". The whole time I was thinking "but why??".

The WASM side of it is really interesting for me as a Xamarin proponent, because it has the potential of true single shared-codebase between mobile and web. I'm not sure why I would use Blazor right now though.

[ Parent | on HN ]
Re:Blazor – Build client web apps with C# by asdfman123 on Wednesday October 02, 2019 @11:15AM (#21137338)
> I went to a meetup focusing on Blazor recently and was really surprised when I found out that Blazor is not "run C# in a browser using WASM" like I thought, but was instead "use your browser as a thin client to C# on the backend

That's not true. It can run client-side on a WebAssembly-based .NET runtime or server-side in ASP.NET core.

I find MS has generally been taking a Manhattan-project style approach these days, trying everything at once and keeping what sticks.

https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-...

[ Parent | on HN ]
Re:Blazor – Build client web apps with C# by JamesSwift on Wednesday October 02, 2019 @11:33AM (#21137552)
I'm not saying it can't, but the primary focus (and current release) is the server-side version. I didn't realize (before that meetup) that server-side Blazor was even a thing, everything I heard about it before this was that the client-side version _was_ Blazor.

I don't know if thats a disconnect in marketing, or me not paying attention, but like I said I was really confused.

[ Parent | on HN ]
Re:Blazor – Build client web apps with C# by asdfman123 on Wednesday October 02, 2019 @11:51AM (#21137782)
Yeah, a confusing spate of offerings and terminology is just part of working with the Microsoft stack. It took me like 3 years of professional C# development to finally sort it all out.

But the reason they're pushing server-side Blazor is because loading client-side Blazor just takes too long in production deployments. Right now, you have to wait several seconds before the page loads, which is unacceptable for most users. I feel like server-side has to be the future, though, and they'll address the speed issue soon enough.

[ Parent | on HN ]
Re:Blazor – Build client web apps with C# by arisAlexis on Wednesday October 02, 2019 @07:18PM (#21141808)
what's the difference between server side and just serving everything on the server and jQuery? sounds very similar
[ Parent | on HN ]
Re:Blazor – Build client web apps with C# by JamesSwift on Wednesday October 02, 2019 @08:13PM (#21142221)
Blazor server-side maintains a websocket to a running client and does some Magic to communicate DOM updates to the client.
[ Parent | on HN ]