but you are selling your consultations, you do this for money, you are not into this you want to be infogypsy, why you dont work in microsoft if you are so good, bewcause you are not
So, a 1 hour video that tells me that I made the best choice by going with Blazor :^) I definitely recommend WebAssembly though since that SignalR requirement for Blazor Server is a big NO. I tried it first and it was unusable from anything mobile since it constantly had to get the user to refresh the connection every time they loaded their browser. WebAssembly takes about 5 to 10 seconds on 5G and then it's cached for next time and it's still faster than my old WebForms version of the app!
Well i am biased towards Blazor. But thats an interesting experience you had using Blazor for mobile. I will need to test it on an actual phone instead of emulation to find the issues you are having and possibly make a video on that. Thanks so much for the feedback. I hope you at least enjoyed the video.
@@justblazorprogramming My web application is one that our employees will be in and out of throughout the day. But every time they close the browser it would disconnect all TCP connections. When they open it a few minutes later, it would ask them to reload since it could not reconnect itself. I tried looking for a way to just get the page to refresh on its own, but it seems that it's deep inside the Blazor js code. I even wanted to just replace the message with my own but couldn't find a way. I haven't checked out .NET 7 to see if they changed this. The only issue I had with the WebAssembly version is that you don't get any upgrades to the client app code if the user never hits refresh. So you have to add a bit of version tracking via an API call and force a page refresh if your app has a newer version sitting on the server. Of course, this problem only happens while you're developing and publishing new versions all the time. I definitely enjoyed your videos. Especially the ones on authentication. Took me a few days of hair pulling to get that working in the wasm project. Turns out it was a conflict between DataContract Json serialization in my web api's and the new System.Text.Json being completely incompatible and all my properties coming through as nulls.
hey, in my case initial loading is no worries. but do the UI face any burden due to wasm? cz i am on razor , love it but i would love it to go spa. Thankyou!!
Angular is actually my favorite framework, yeah its a bit hard to learn but it pays off at the end Angular front-end + .NET back-end is my favorite stack to work with, im hoping Blazor will improve in performance soon so i can finally get as far away from javascript as possible Hopefully Blazor united delivers on that much needed performance
I do care, and i can tell you this, Blazor has slower performance than Angular or React. Even with the optimizations, Blazor WASM still has the loading issue it has had, it might be better, you might find ways to not make the user see that is what is happening via pre-rendering, but Blazor is still perfomance-wise compared to these other frameworks slower. I didnt go into the numbers because its obvious when you run a Blazor App that it is at least without pre-rendering.
@@justblazorprogramming I see... Sorry for my rude words - I just deleted them. Though for the time being I guess Blazor doesn't make much sense except as part of MAUI apps
Its fine, just you know, try to be a little more polite next time. Blazor has a purpose in the fact that now there is a viable alternative to creating SPA's/complex Web Apps without the need of having a whole different language in your skillset, and if you were already a .NET shop you would probably want something like this if you need to move from an older technology to something more modern as easy as possible. It may not be the most optimal of the trio in the sense of performance, but you can absolutely build as many things as you would in those other frameworks and not have to go outside C# in a meaningful way. Theres value in time for developers trying to use the technology and having them get into something that is familiar like Blazor saves time and money overall.
I agree in part, Webassembly needs to be further optimized, however the reason why i believe in its competitive edge is the mere fact you dont need JS to begin using it. .Net is a very big part of the market and making something catering to them thats near-peer to the competition already existing and also something that can also be applied to mobile development is a lot for a framework to do. I have hope for this initial load issue to be fixed or at least get far more optimized as time goes on as Microsoft keeps investing in it. Dont give up on it just yet, is what im saying.
This video should easily be only 13 minutes long! The other 49 minutes is just a bunch of BS and blah blah blah! Nothing said that is really worth listening to!
but you are selling your consultations, you do this for money, you are not into this you want to be infogypsy, why you dont work in microsoft if you are so good, bewcause you are not
Of course i do this for the money.
So, a 1 hour video that tells me that I made the best choice by going with Blazor :^) I definitely recommend WebAssembly though since that SignalR requirement for Blazor Server is a big NO. I tried it first and it was unusable from anything mobile since it constantly had to get the user to refresh the connection every time they loaded their browser. WebAssembly takes about 5 to 10 seconds on 5G and then it's cached for next time and it's still faster than my old WebForms version of the app!
Well i am biased towards Blazor. But thats an interesting experience you had using Blazor for mobile. I will need to test it on an actual phone instead of emulation to find the issues you are having and possibly make a video on that. Thanks so much for the feedback. I hope you at least enjoyed the video.
@@justblazorprogramming My web application is one that our employees will be in and out of throughout the day. But every time they close the browser it would disconnect all TCP connections. When they open it a few minutes later, it would ask them to reload since it could not reconnect itself. I tried looking for a way to just get the page to refresh on its own, but it seems that it's deep inside the Blazor js code. I even wanted to just replace the message with my own but couldn't find a way. I haven't checked out .NET 7 to see if they changed this.
The only issue I had with the WebAssembly version is that you don't get any upgrades to the client app code if the user never hits refresh. So you have to add a bit of version tracking via an API call and force a page refresh if your app has a newer version sitting on the server. Of course, this problem only happens while you're developing and publishing new versions all the time.
I definitely enjoyed your videos. Especially the ones on authentication. Took me a few days of hair pulling to get that working in the wasm project. Turns out it was a conflict between DataContract Json serialization in my web api's and the new System.Text.Json being completely incompatible and all my properties coming through as nulls.
hey, in my case initial loading is no worries. but do the UI face any burden due to wasm? cz i am on razor , love it but i would love it to go spa. Thankyou!!
In VS you can configure Blazor to hot reload upon saving the files.
Angular is actually my favorite framework, yeah its a bit hard to learn but it pays off at the end
Angular front-end + .NET back-end is my favorite stack to work with, im hoping Blazor will improve in performance soon so i can finally get as far away from javascript as possible
Hopefully Blazor united delivers on that much needed performance
hmmmm a channel called just 'blazor programming'. I wonder if he'll be biased
Should watch the video and find out if i address it
The channel creator telling me to watch their video, sounds like bias 😛
You should make a discord server. Anybody live near Eau Claire WI and lookin to write Blazor on the weekends together?
I do have one its in the description
@@justblazorprogramming oh I didn't see that! What's the name of the server? Can't say I'm willing to take the 50/50 on another programmers link lol
Just Blazor Programming thats the server name. Idk if its public or not cause i have limited invites that expire
Muchas gracias.
You haven't given a damn about promised performance comparison
I do care, and i can tell you this, Blazor has slower performance than Angular or React. Even with the optimizations, Blazor WASM still has the loading issue it has had, it might be better, you might find ways to not make the user see that is what is happening via pre-rendering, but Blazor is still perfomance-wise compared to these other frameworks slower. I didnt go into the numbers because its obvious when you run a Blazor App that it is at least without pre-rendering.
@@justblazorprogramming I see... Sorry for my rude words - I just deleted them.
Though for the time being I guess Blazor doesn't make much sense except as part of MAUI apps
Its fine, just you know, try to be a little more polite next time. Blazor has a purpose in the fact that now there is a viable alternative to creating SPA's/complex Web Apps without the need of having a whole different language in your skillset, and if you were already a .NET shop you would probably want something like this if you need to move from an older technology to something more modern as easy as possible. It may not be the most optimal of the trio in the sense of performance, but you can absolutely build as many things as you would in those other frameworks and not have to go outside C# in a meaningful way. Theres value in time for developers trying to use the technology and having them get into something that is familiar like Blazor saves time and money overall.
There’s a lot of inaccuracies in this video. I think the presenter needs a better understand of his content.
I love blazor. However, till wasam download time is not fixed, blazor is not a serious contender.
I agree in part, Webassembly needs to be further optimized, however the reason why i believe in its competitive edge is the mere fact you dont need JS to begin using it. .Net is a very big part of the market and making something catering to them thats near-peer to the competition already existing and also something that can also be applied to mobile development is a lot for a framework to do. I have hope for this initial load issue to be fixed or at least get far more optimized as time goes on as Microsoft keeps investing in it. Dont give up on it just yet, is what im saying.
This video should easily be only 13 minutes long! The other 49 minutes is just a bunch of BS and blah blah blah! Nothing said that is really worth listening to!
You gave me a great idea, thanks.