Blazor United -- I love it. Especially the auto mode for first-time vs cached. More often than not, projects evolve into something bigger than the original design. And when they do, starting from a project type such as this, affords the flexibility without having to completely change the architecture. For that reason alone, I think this adds tremendous value! Steve's new super mega thing
You guys took it one step ahead, it's incredible! People were asking if it was possible to support Blazor Server and WebAssembly side-by-side in the same app. Now you made their choice for them!
This is it right here. The automatic switchover from Blazor Server to Blazor WASM once assemblies are downloaded is the killer feature that's going to make Blazor a viable option for A LOT more use cases.
This is nuts. You've covered all of the disadvantages to Blazor WASM and made it all magic. And you can spin it all up without the heavy lifting of something like React. Also, the "server side" devs won't fear it.
Steve please make this channel live and running, we love and miss your voice, style, and simplicity. please please, we need to listen to you regularly.
I love where this is headed. Using Blazor for public-facing websites came with trade-offs until now, but this makes it a no-brainer! Giving developers control over render modes is perfect, abstracting that away behind magic would be a regression imho. I do hope that the server-rendered bits do not suffer from the circuit-server pinning challenges that come with Blazor server. That's the biggest challenge with Blazor Server for us currently, as it makes load balancing and deploying updates very difficult.
It would be cool if you guys could add SSG (Static Site Generation), ISR (Incremental Static Regeneration), On Demand ISR. Really looking forward for this. Anyway, I feel like it's the time to invest time in Blazor. Great work.
This is what I've been waiting for. This component architecture we had a little bit with webform. Always wondered why it had to be different. Lovely, just lovely. How can we accelerate this. I hope we done have to wait for next dotnet release. Please please let this come very soon. I so cant wait.
Steve, you are a god! This was the missing link that would make Blazor truly the number 1 choice for frontend, with absolutely no disadvantages from my point of view!
Amazing!! Mind-blown emoji. We use pre-rendering right now to improve the load time of our Blazor wasm apps. Better user experience and critical for SEO, but there’s still the Blazor initialization delay. It’d be amazing to move this to the background. Any plans to take advantage of this new progressive/auto feature to benefit this scenario? I’d be amazing to render on the server for SEO and speed, but then transition to WASM in the background, avoiding the Blazor WASM initialization delay.
More importantly, it is great to hear directly from Mr Steve Sanderson via this channel, the architect of Blazor and one of my favorite devs and a genius. Hope he presents more content here, it will be very helpful. Thanks Steve!
This is amazing. We use blazor server side for the reduced dev effort for POC but has the shortcoming of scaling up to users, you have now solved that with us being able to program hot pages as static content ♥️
This is really good stuff, Steve. Very relevant to what we're doing and would undoubtedly help us greatly if something like this makes it to production.
This is something I've wanted for a long time. Thank you for taking the obvious next step to making "real" server-side blazor work. I love the freedom of choice too, there are definitely scenarios where having these types of choices makes a ton of sense.
I've been developing in Blazor WASM for several months and what you've presented here is fantastic! I am using several third party Blazor components now, however, so I hope this will work seamlessly with those.
Brilliant work! I have been experimenting with combining Razor components for the login process of my Blazor apps so the WebAssembly can only be downloaded by authenticated users but your work with Blazor United looks much more practical and extensible. So excited to keep it all in the Blazor pages/components.
It would be amazing if we could use WebAssembly mode only when an internet connection isn’t available (to enable offline mode/PWA), but use Server mode otherwise-this way we could get all the benefits of Server when online (like directly access DB, without need for an API) but still get offline capability. I hope if “United” makes it to production, this use case will be supported.
This is really great idea! And I think you can also add some attributes like AtClient AtServer where Blazor components preferably be rendered. So, you can render whole pages and "big" things at server and use wasm to interact with controls and JavaScript at client side. Sometimes you expect region of the page to behave like SPA, but the application overall use server-side rendering. This way you can open several tabs on your browser and be in the same context, but not necessarily synchronize some wasm stuff, which mostly designed to interface interactions.
Love it. Thank you Steve and to your team! Amazing things from Blazor team. This clearly shows the power and flexibility of Blazor and .NET technologies!!!
I lead my company’s innovation developer group and focus on extreme agile developed prototypes. We are highly focused on delivering as fast as possible and this sort of framework is perfect for what we do. Very excited for preview releases!
Oh I want this. It would sure be a lot easier than the huge amount of js/ajax we have to write to mimic an SPA and still keep our SEO for our public pages. Great stuff.
Definitely need that last bit. My latest project is actually two builds, blazon server side and wasm. For most landing or first visits, I use server side. For users for paid or specific application within my web app, i route them to the wasm.
No one can beat Blazor now. This is the best thing happening right now. I need something this for one of the project I am working on. I am using Blazor server but I do not want ws. And now you are working on it, So Thank You for this great addition to the Blazor. Waiting this to be released
This is amazing Steve! You get the best of both worlds. I do wonder if it's possible to somehow transition to webassembly using the auto mode when it's finished downloading and starting up the runtime? That'd be awesome as you'll save resources and the user gets fast interactivity time. Really love that it's a per component basis though, this means I could essentially just put islands of Blazor server where appropriate (e.g. Payments, real-time components like Dashboards and chat etc...)
Blazor United -- I love it. Especially the auto mode for first-time vs cached. More often than not, projects evolve into something bigger than the original design. And when they do, starting from a project type such as this, affords the flexibility without having to completely change the architecture. For that reason alone, I think this adds tremendous value! Steve's new super mega thing
now I'm hyped!! I can't wait for Blazor United.
You guys took it one step ahead, it's incredible! People were asking if it was possible to support Blazor Server and WebAssembly side-by-side in the same app. Now you made their choice for them!
Wow, steve I am speechless. We are all blessed to have you. 😁
This is everything I've ever wanted from Blazor for web. Holy moly.
This is it right here. The automatic switchover from Blazor Server to Blazor WASM once assemblies are downloaded is the killer feature that's going to make Blazor a viable option for A LOT more use cases.
This is nuts. You've covered all of the disadvantages to Blazor WASM and made it all magic. And you can spin it all up without the heavy lifting of something like React. Also, the "server side" devs won't fear it.
Steve please make this channel live and running, we love and miss your voice, style, and simplicity. please please, we need to listen to you regularly.
I keep watching this over and over again. Mind blown.
This is really REALLY cool stuff, Steve 🤩🔥
I love where this is headed. Using Blazor for public-facing websites came with trade-offs until now, but this makes it a no-brainer! Giving developers control over render modes is perfect, abstracting that away behind magic would be a regression imho.
I do hope that the server-rendered bits do not suffer from the circuit-server pinning challenges that come with Blazor server. That's the biggest challenge with Blazor Server for us currently, as it makes load balancing and deploying updates very difficult.
+1
It would be cool if you guys could add SSG (Static Site Generation), ISR (Incremental Static Regeneration), On Demand ISR. Really looking forward for this. Anyway, I feel like it's the time to invest time in Blazor. Great work.
I see what you're upto Steve. Simplifying blazor to almost only HTML. This should have broad appeal. Magnificent stuff bro.
This is what I've been waiting for. This component architecture we had a little bit with webform. Always wondered why it had to be different. Lovely, just lovely. How can we accelerate this. I hope we done have to wait for next dotnet release. Please please let this come very soon. I so cant wait.
Steve, you are a god! This was the missing link that would make Blazor truly the number 1 choice for frontend, with absolutely no disadvantages from my point of view!
This is trully amazing!!! It opens up the possibility to manage resources and interactions - something HIGHLY desired! Thank you!
Amazing!! Mind-blown emoji. We use pre-rendering right now to improve the load time of our Blazor wasm apps. Better user experience and critical for SEO, but there’s still the Blazor initialization delay. It’d be amazing to move this to the background. Any plans to take advantage of this new progressive/auto feature to benefit this scenario? I’d be amazing to render on the server for SEO and speed, but then transition to WASM in the background, avoiding the Blazor WASM initialization delay.
More importantly, it is great to hear directly from Mr Steve Sanderson via this channel, the architect of Blazor and one of my favorite devs and a genius. Hope he presents more content here, it will be very helpful. Thanks Steve!
This is the right direction - Blazor United. It could be the default when it's finally released in .NET 8. I don't see why not....
Brilliant. This must be the default for new project templates when its GA. Great job :-)
Steve is the ultimate GOAT 🐐
The "auto" mode is awesome!!!
You and your team are doing really amazing job!
This is going to be a great channel, Steve. we are waiting those features long ago. GREAT STUFF.
This is amazing. We use blazor server side for the reduced dev effort for POC but has the shortcoming of scaling up to users, you have now solved that with us being able to program hot pages as static content ♥️
This is really good stuff, Steve. Very relevant to what we're doing and would undoubtedly help us greatly if something like this makes it to production.
Speechless. Great feature! I've been looking for something like this, and it's like you guys read my mind
This is perfect! best of all worlds - literally cannot wait for it to be ready!
Impressive work, this is very much needed to harmonise the options available and allow flexibility at a page level - cannot wait to see this released!
This is really awesome! I think this would make a huge impact to teams.
This direction looks great. Also your presentations are stellar, always concise, on-point, informative. Thank you very much.
This is mind-blowingly amazing! 🎉🎉 🤩
I love it! Can’t wait to use this!
This is something I've wanted for a long time. Thank you for taking the obvious next step to making "real" server-side blazor work. I love the freedom of choice too, there are definitely scenarios where having these types of choices makes a ton of sense.
What a man you are Steve! Simply amazing! 🙌🙌🙌
I've been developing in Blazor WASM for several months and what you've presented here is fantastic! I am using several third party Blazor components now, however, so I hope this will work seamlessly with those.
12:13 mind blown.
This is all amazing, love it! keep up the good work, thank you.
100% onboard, making it easier to code in (mostly) one language, one framework, for all devices and business requirements. Love it!
Brilliant work! I have been experimenting with combining Razor components for the login process of my Blazor apps so the WebAssembly can only be downloaded by authenticated users but your work with Blazor United looks much more practical and extensible. So excited to keep it all in the Blazor pages/components.
You hit it right on the nose. This is exactly the kind of thing our team is looking for, well done!
Really really looking forward to this!
We have been waiting for this, hopefully it is coming out soon. Good job
That's more than awesome, that's just fantastic! Thank You, Steve!
It would be amazing if we could use WebAssembly mode only when an internet connection isn’t available (to enable offline mode/PWA), but use Server mode otherwise-this way we could get all the benefits of Server when online (like directly access DB, without need for an API) but still get offline capability. I hope if “United” makes it to production, this use case will be supported.
This is absolutely beautiful
Brilliant! I cannot wait for this to become available.
We've just seen a preview of the amazing future of web development. Thank you!
I'm all for this. Yes, please!
This is awesome . Great work !
steve - its very freakin relevant. love this approach!
omg! This looks amazing!
This is awesome! Seriously! 🎉
This is really great idea! And I think you can also add some attributes like AtClient AtServer where Blazor components preferably be rendered. So, you can render whole pages and "big" things at server and use wasm to interact with controls and JavaScript at client side. Sometimes you expect region of the page to behave like SPA, but the application overall use server-side rendering. This way you can open several tabs on your browser and be in the same context, but not necessarily synchronize some wasm stuff, which mostly designed to interface interactions.
this would be a game changer for blazor. kudos to the blazor team, would love to try this when preview comes out.
Unbelievably cool!
Absolutely relevant to my usage, I can't wait for it to come out.. :)
Very exciting and looking forward to Blazor United.
Exactly what i wanted. Thank you.
Fantastic primer. Looking forward to seeing that deploy to prod.
this is game changing for web development and developers
This is so great stuff. Specially the auto mode. For me the auto mode is so smart and a game changer for blazor.
That sounds so amazing 😍
This is excellent, I love it
magnificent -- thank you Steven
looking forward to testing it!
Love it. Thank you Steve and to your team! Amazing things from Blazor team. This clearly shows the power and flexibility of Blazor and .NET technologies!!!
Honestly this is very exciting, I wonder how things like local storage would work for users and how libraries would interact with this
I'm speechless and I cannot wait to test drive this!
Loved it! That's the future web!
Awesome stuff, can't wait to try it!
Looks great. Looking forward.
Wow this looks extremely cool.
I may have to start supporting Blazor Utd....
I lead my company’s innovation developer group and focus on extreme agile developed prototypes. We are highly focused on delivering as fast as possible and this sort of framework is perfect for what we do. Very excited for preview releases!
We need this in production!
That could be amazing outcome desired by many. Hope idea will success
It's a great news, hope it will be released in next .NET 8.0 without any delay :D
I was thinking about it for a while...and here we have this news
Oh I want this. It would sure be a lot easier than the huge amount of js/ajax we have to write to mimic an SPA and still keep our SEO for our public pages. Great stuff.
This gives me flashbacks to WebForms Runat=Server
Me too. The ubiquitous `runat="server"`
Excelent feature. Thanks for share.
OMG this is amazing!
Great stuff Steve!
WOW!!!!! This is really awesome
This is awesome!
Definitely need that last bit. My latest project is actually two builds, blazon server side and wasm. For most landing or first visits, I use server side. For users for paid or specific application within my web app, i route them to the wasm.
Coolness... Love the 'auto' mode!
A really good idea!
Wow, awesome Steve. Let's bring it in.
Basically solves any complaints I had with Blazor
No one can beat Blazor now. This is the best thing happening right now. I need something this for one of the project I am working on. I am using Blazor server but I do not want ws. And now you are working on it, So Thank You for this great addition to the Blazor. Waiting this to be released
This looks really useful!
This channel will be very interesting, I really like blazor.
This is amazing Steve! You get the best of both worlds. I do wonder if it's possible to somehow transition to webassembly using the auto mode when it's finished downloading and starting up the runtime? That'd be awesome as you'll save resources and the user gets fast interactivity time. Really love that it's a per component basis though, this means I could essentially just put islands of Blazor server where appropriate (e.g. Payments, real-time components like Dashboards and chat etc...)
Soooooooooooooooooo Excited!!!!
Steve, we need more videos from you!
Just when I thought I was out, they pull me back in!
Nice, I cannot wait!
Outstanding 🤩
Amazing future for Blazor
Wow. So great. Thank you!