I have also noticed hot reload is improved. Making changes in css files used to work before but even some slight change in a method would require to stop the app. Now, most of the time it works without any issues. Change value of variable, create new methods, add new lines, it work without any issues.
Great updates, I have used Blazor hybrid for our internal org app and I was able to build entire app in a couple of days. Do you know if it is a good idea to build any public apps using Blazor, and also why it is not being welcomed by the startups :(
Thank you! Great questions. I think Blazor can be used for any app - from small to enterprise - it is just such an excellent technology in my opinion. Startups seem to love JavaScript based frameworks and Python based frameworks and large corporates seem to love Java or .NET. One reason could be because startups tend to hire younger developers and can perhaps pay them less. JavaScript is easier to learn and more JavaScript developers are generally more available. There is definitely a perceived higher learning curve for .NET and C#. That is just one reason - I'd love to get more feedback from anyone who reads this comment. I think its an interesting question :)
The CSS caching issue is perhaps a bit dependant on how assets are accessed. e.g. if the rendered url automatically appends something like a ?v=nonce that is , say... an SHA256 value of the file itself... then the request will be unique and cache problems avoided. Of course, if using a CDN or frontend, then needing to cache by unique URL is a given.
I find Blazor to be OK for "business" web-apps, but when wanting to do something "special" on the front-end or when needing reliable HTML compliance, I find myself gravitating back to TS/JS and frameworks like Vue. How much of that is simply a case of being familiar with one tool vs another to solve the same problem... I'm not sure - but I haven't yet found a compelling case to change hammers and use Blazor instead of the "traditional" alternative.
Not too happy with .NET 9 and Blazor upgrade at the moment - our web app stopped working due to SkiaSharp incompatibilities - so it still needs some work. Also had issues with publishing. Had to rollback to .NET 8 which works fine.
Sorry to hear about that. Thanks for commenting about this. Hopefully these issues will be fixed soon in .NET 9 :) It must be very frustrating that you have to rollback to .NET 8.
The video is about the impact of .NET9 on Blazor. .NET Aspire 9 shipped with .NET 9 and can provide significant benefits to Blazor applications - a basic example has been included to illustrate this point. There is also a lot of other information presented in the video about improvements made in .NET 9 that directly affect Blazor.
@@GavinLon Visual Studio frequently encounters issues with syntax highlighting for Blazor. It fails to bold tags or recognize components properly, often requiring a restart to resolve. Additionally, the HTML and CSS suggestions are terrible-when opening a tag, it sometimes auto-inserts an unrelated component tag instead. When writing the @if syntax, it arbitrarily inserts a # in the middle, turning it into @#if, which then needs to be manually corrected. These minor yet persistent bugs severely degrade the Blazor coding experience, making it slow and frustrating to work with.
@minhgiangho1410 Okay thanks for clarifying these issues that you have had with Visual Studio regarding Blazor development. I'll see if I can replicate them myself. I must say I've been happy with my experience in developing Blazor apps using Visual Studio.
When working on a slower computer i notice these issues, but not from my main workstation..NET9 also resolved some of those issues. I still do get slowed down from those unwanted suggestions tho.
Blazor is a piece of shit that not only delivers a subpar experience for the end user from what's already widely used in frontend (React, Angular, Svelte, Vue, etc) by either adding server latency or being slower by being bloated .NET infused web assembly. But wait there's more! It also makes the developer experience worse by requiring Visual Studio for frontend (anybody who tried this knows its not fun), and you end up needing JS anyways and it's so annoying having to do JS Interop in Blazor. So in that sense it's got the true Microsoft signature effect: someone somewhere pulling their hair out going "this isn't working why the f*ck would anyone do this" 👍
Yeah, I somewhat agree. For me I am willing to ignore the performance issues because of the ease of use especially with the new Web app + Blazor MAUI template, I can code once and can deploy it in every platform. Also, you can technically use vs code and rider if you want. I honestly prefer rider.
@@ggcc3261 Not really. For example I am just one person. If I wanted to it "properly" then I would have used react or svelte for web, swift for iOS and MacOs, Kotlin for Android etc. you see the issue with that? Users don't care if your app is a few milliseconds faster because of the "perfect" tech stack - they care if it solves their problem and works well. The extra complexity of juggling all these technologies just isn't worth it when the difference in user experience is minimal. Keep it simple and focus on shipping something useful. Don't try to impress other software engineers.
Non blazor users seem to bash on it a lot, while those who use blazor are happy with what they have. Says alot about you JS monkeys 😂. Either way, I'm not here to hate on tools. If you are happy with old and still going, time checked JS and it's frameworks, that's perfect, but it doesn't mean blazor is bad. It might not be as good in some ways, but for me personally, when I mainly studied C#, it's a better option for building apps than learning JS from the start. And it's also easy and fast and it has great libraries as well (Syncfusion for example). No need to hate on it.
Thank you very much for the comprehensible narration.
You are very welcome! I appreciate your positive feedback. Thank you :)
I have also noticed hot reload is improved. Making changes in css files used to work before but even some slight change in a method would require to stop the app. Now, most of the time it works without any issues. Change value of variable, create new methods, add new lines, it work without any issues.
Great point. I should have mentioned hot reload in the video. I've also noticed an improvement there. Thank you! :)
HotReload suck
Great updates, I have used Blazor hybrid for our internal org app and I was able to build entire app in a couple of days. Do you know if it is a good idea to build any public apps using Blazor, and also why it is not being welcomed by the startups :(
Thank you! Great questions. I think Blazor can be used for any app - from small to enterprise - it is just such an excellent technology in my opinion. Startups seem to love JavaScript based frameworks and Python based frameworks and large corporates seem to love Java or .NET. One reason could be because startups tend to hire younger developers and can perhaps pay them less. JavaScript is easier to learn and more JavaScript developers are generally more available. There is definitely a perceived higher learning curve for .NET and C#. That is just one reason - I'd love to get more feedback from anyone who reads this comment. I think its an interesting question :)
The CSS caching issue is perhaps a bit dependant on how assets are accessed. e.g. if the rendered url automatically appends something like a ?v=nonce that is , say... an SHA256 value of the file itself... then the request will be unique and cache problems avoided. Of course, if using a CDN or frontend, then needing to cache by unique URL is a given.
Cool - thanks for your feedback :)
I find Blazor to be OK for "business" web-apps, but when wanting to do something "special" on the front-end or when needing reliable HTML compliance, I find myself gravitating back to TS/JS and frameworks like Vue. How much of that is simply a case of being familiar with one tool vs another to solve the same problem... I'm not sure - but I haven't yet found a compelling case to change hammers and use Blazor instead of the "traditional" alternative.
Great - thank you for sharing your thoughts :)
Not too happy with .NET 9 and Blazor upgrade at the moment - our web app stopped working due to SkiaSharp incompatibilities - so it still needs some work. Also had issues with publishing. Had to rollback to .NET 8 which works fine.
Sorry to hear about that. Thanks for commenting about this. Hopefully these issues will be fixed soon in .NET 9 :) It must be very frustrating that you have to rollback to .NET 8.
This video is supposed to be about Blazor, not Aspire...
The video is about the impact of .NET9 on Blazor. .NET Aspire 9 shipped with .NET 9 and can provide significant benefits to Blazor applications - a basic example has been included to illustrate this point. There is also a lot of other information presented in the video about improvements made in .NET 9 that directly affect Blazor.
Visual Studio is extremely bad for Blazor
Why do you say that? :) I find Visual Studio to be the best tool for creating Blazor applications.
@@GavinLon Visual Studio frequently encounters issues with syntax highlighting for Blazor. It fails to bold tags or recognize components properly, often requiring a restart to resolve. Additionally, the HTML and CSS suggestions are terrible-when opening a tag, it sometimes auto-inserts an unrelated component tag instead. When writing the @if syntax, it arbitrarily inserts a # in the middle, turning it into @#if, which then needs to be manually corrected. These minor yet persistent bugs severely degrade the Blazor coding experience, making it slow and frustrating to work with.
@minhgiangho1410 Okay thanks for clarifying these issues that you have had with Visual Studio regarding Blazor development. I'll see if I can replicate them myself. I must say I've been happy with my experience in developing Blazor apps using Visual Studio.
When working on a slower computer i notice these issues, but not from my main workstation..NET9 also resolved some of those issues. I still do get slowed down from those unwanted suggestions tho.
@@cirusMEDIA What's considered a slower computer, CPU/memory wise?
Microsoft will never use it for real big apps.
Yes, office 365 still use asp webform😂
Blazor is a piece of shit that not only delivers a subpar experience for the end user from what's already widely used in frontend (React, Angular, Svelte, Vue, etc) by either adding server latency or being slower by being bloated .NET infused web assembly. But wait there's more! It also makes the developer experience worse by requiring Visual Studio for frontend (anybody who tried this knows its not fun), and you end up needing JS anyways and it's so annoying having to do JS Interop in Blazor.
So in that sense it's got the true Microsoft signature effect: someone somewhere pulling their hair out going "this isn't working why the f*ck would anyone do this" 👍
Yeah, I somewhat agree. For me I am willing to ignore the performance issues because of the ease of use especially with the new Web app + Blazor MAUI template, I can code once and can deploy it in every platform. Also, you can technically use vs code and rider if you want. I honestly prefer rider.
"A bad workman blames his tools."
@@rankarat a bad workman uses the inferior tool out of incompetence and/or fear of the appropriate tool
@@ggcc3261 Not really. For example I am just one person. If I wanted to it "properly" then I would have used react or svelte for web, swift for iOS and MacOs, Kotlin for Android etc. you see the issue with that? Users don't care if your app is a few milliseconds faster because of the "perfect" tech stack - they care if it solves their problem and works well. The extra complexity of juggling all these technologies just isn't worth it when the difference in user experience is minimal. Keep it simple and focus on shipping something useful. Don't try to impress other software engineers.
Non blazor users seem to bash on it a lot, while those who use blazor are happy with what they have. Says alot about you JS monkeys 😂. Either way, I'm not here to hate on tools. If you are happy with old and still going, time checked JS and it's frameworks, that's perfect, but it doesn't mean blazor is bad. It might not be as good in some ways, but for me personally, when I mainly studied C#, it's a better option for building apps than learning JS from the start. And it's also easy and fast and it has great libraries as well (Syncfusion for example). No need to hate on it.