12,203 karma · joined July 29, 2008
jason@...
https://vyrotek.com
https://x.com/vyrotek
https://vyrotek.itch.io
It seems to look very similar but I didn't see whether LiveView has the "sticky" websocket server requirement like Blazor. With Blazor all of the user's state is in memory on one specific app server. And if a connection is lost the app is completely unresponsive.
It's a great dev experience but I've seen comments about scaling and interaction latency concerns. Seems like it'd be great for intranet corp apps.
Is anyone running either tech as a public facing service?
And yes, it was amazing. And so was the phone.
https://fluent2.microsoft.design/components/web/react/button...
I think what makes it stick is that it's more than just a game. It's a social space where my kids jump in to sometimes just to chat with their friends from school. Reminds me of hanging out in Team Fortress 2 game servers and just chatting while casually screwing around in the game.
Here's the interview where those stats came from for those curious.
https://venturebeat.com/games/how-gorilla-tag-made-it-big-on...
The various hybrid/mpa/spa innovations are great but not everyone needs them. It's sad to see the traditional SPA approach be discouraged so much.
These meta-frameworks crossing into the server-side will raise a lot of architectural questions for teams. For us, we have React SPAs served by ASP.NET backends and using Vite locally. We'd rather not adopt another dependency like Next or Remix. We're definitely not going to adopt any Node on the backend.
The friction we're experiencing with these new static-exports is that we'd have to configure the backends with the front-end framework's routing system in order to serve the split out static files. e.g. ASP.NET needs to know how to serve NextJS's folder/file/path structure. As opposed to today where we just have to serve an index.html file regardless of whether it's Ang, React, Svelte, etc.
Thank you for your efforts! I just recently discovered it. It looks like a breath of fresh air for those of us who have been doing this stuff for a long time.
As you said, discoverability is probably the only reason why it's not more well known. There are devs who haven't ventured out of React for their entire careers and don't know to look for better tools for different problems.
Also, been recently playing with ways to generate API code plumbing without any schema layers. (Swagger/OpenAPI/Proto) [1]
"Cathie Wood of ARKK sold 160,887 shares of Coinbase, COIN, today."
https://twitter.com/unusual_whales/status/163833492762331136...
NextJS and RemixJS have interesting approaches to gluing clients and server together. Microsoft Blazor Server is an extreme version of where things are headed. Just call C# functions and the UI is surgically updated as needed over SignalR. I haven't found any other stacks take it that far yet.
Not quite sure how it works beyond that when you need multiple service instances connected with a backplane. The new premium tier I just saw sounds convenient though.
https://azure.microsoft.com/en-us/pricing/details/signalr-se...
Is your project an internal app or public?
I'm cautiously optimistic about Blazor Server but I'm not sure I like the sticky SignalR requirement. The expectation seems to be that the backend server will keep around a lot of state (cough viewstate?) in memory associated to that session. It's a very convenient dev experience for sure, but it seems difficult to scale beyond internal business apps.
I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.