21–30 of 37 posts
Blazor United looks ambitious but sounds great! The goal feels similar to that of Remix.run and a few other frameworks that are blending SPA/SSR. I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.
I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…
The trick is to start the company yourself. :) We're 3 years in and full .NET stack. 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,…
Earlier quoted context omitted.
The trick is to start the company yourself. :) We're 3 years in and full .NET stack. 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,…
dev on .net is something I can understand ... but deploying and running windows servers in prod sounds like a hellish nightmare
I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…
Which can be avoided with Blazor WASM that has different trade-offs with poor start times & SEO. Hopefully something that can be resolved with their upcoming Blazor United solution, which I'm assuming means no longer being able to host Blazor WASM's static assets from a CDN.
Earlier quoted context omitted.
The trick is to start the company yourself. :) We're 3 years in and full .NET stack. 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,…
dev on .net is something I can understand ... but deploying and running windows servers in prod sounds like a hellish nightmare
Blazor United looks ambitious but sounds great! The goal feels similar to that of Remix.run and a few other frameworks that are blending SPA/SSR. I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.
* Unclear state management story in Blazor WASM. There is a flux lib for Blazor but.. Ugh, I'm spoiled by MobX. Another project, Cortex.Net, inspired by MobX and uses Fody to make seamless fine-grain change subscriptions looked promising but the project did not gain traction :(
* Unclear runtime extensibility: How can I "plug-in" Blazor components that were not present at build time? That's a ASP.NET challenge in general TBH.
I REALLY want to want to use it though. That sweet, sweet isomorphism.
I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…
It also allows to add real-time functionality in a breeze. Even business applications can profit from that, but you often just skip that because it is not worth the effort.
I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…
What kind of setup do you have to avoid users noticing the drop of their websocket connection due to a deployment? Blazor Server development experience is very good, but even for an intranet application, it can have a poor user experience by default due to the requirement of a persistent connection.
Earlier quoted context omitted.
It's worth the work heading to System.Text.Json - even if only to make staying up with .NET easier for yourself. It had a bit of a rough start but it seems far more interoperable on weird edge cases than Newtonsoft now, so all the "Newtonsoft-y" things you're doing might evaporate.
Isn't Text.json also faster at this point because it uses all the new span goodness and the like?
Pretty cool!