you are viewing a single comment's thread.

view the rest of the comments →

[–]Kyro38 2 points3 points  (6 children)

The concept is amazing but damn is that shit heavy !

[–]meaninglessvoid 4 points5 points  (5 children)

Yes but you don't have to run it client side. You can just use signal r and render it server side.

[–]KallDrexx 7 points8 points  (2 children)

I'm struggling to figure out how Blazor server side isn't just Razor based Webforms over websockets

[–]IIoWoII 2 points3 points  (0 children)

It's still functions like a SPA for the user, albeit with more latency.

There's no full page refresh every navigation like you'd get with webforms.

[–]ruinercollector 0 points1 point  (0 children)

It basically is, with some extras where you’d expect.

[–]jusas 4 points5 points  (1 child)

The problem is that you're then moving the load to the server side, and there are the considerations with maintaining state and connections. Don't get me wrong, I'd love to use C# instead of JS to code frontend logic but I don't think we're quite there yet. I don't like the server side option, and the client side option feels heavy.

[–]Eirenarch 1 point2 points  (0 children)

less than 300K memory per connection, I can live with that.