Thanks so much! The video comparing Blazor to React seems to be more popular, I guess because React is so popular but actually the comparison between Blazor and Next.JS is a better comparison because React is just a library whereas Blazor and Next.Js are both full web development frameworks where one technology can be leveraged to build a full-stack web application :)
Thank you, Gavin. I believe Blazor will take a leading position in the coming years, especially it is supported by Microsoft. We look forward to seeing practical projects using the latest versions of Blazor.
Yes, I think you might be right! :) I know if I was going to build a professional full stack web application - I would choose Blazor, .NET and C# = especially with the new features and enhancements due to be released with .NET 8. We'll definitely look at practical examples using Blazor on .NET 8 in up coming videos. :)
Blazor especially with ver8. Best of both worlds and the html interaction with c# seems easier to me than js. Developing with Blazor is fun and has a short learning curve. (especially if you know c# or typescript). Good video, thanks.
Hey Kolade!! Great to see you in the comments section of one of my videos (Kolade and I both work for @freeCodeCamp). Thank you for your super positive feedback! I hope you have a fantastic birthday!! All the best!
My background is in JavaScript and I have worked more than 15 years in JavaScript.. but I always prefer statically typed language so I prefer C# and I love blazor. Top of that blazor is way easier to build web apps!
I'm getting a lot of positive feedback about Blazor and I'm glad you mentioned the advantage of using a statically typed language (this advantage should not be underestimated). I agree Blazor is fairly easy to learn, I also think C# is pretty easy to learn too. Great comment, thank you!
@@GavinLon it's super easy, especially with next 13 where you have layout components, but it was already easy with next 12 and earlier. You simply just have to create a folder with the name of the folder in brackets and that's it basically. Layouts are even inherited if you don't create one on the folder level. Edit: one thing that is a little bit tricky with next is nested dynamic routes is a bit confusing because you create them in your pages folder structure it is a bit difficult to visualize, but it does not take much effort to understand it when you need to
Okay thanks for your comment. :) I should have been more clear in my first comment. I think it's probably not as clean or elegant (if you like) when it comes to larger more complex applications. This is just opinion and in some articles others have also expressed this but of course many developers like yourself may disagree with this assertion :)
@@unhandledexception1948 blazor is made for be developers who righteously don’t want to learn js frameworks for frontend. next is made for fe developers who doesn’t want to learn oop based c# to make an api. so the future is full stack development, you just need to decide what tools you’re going to use. if you’re more comfy with c# it makes sense to go with blazor. other than that, next/nuxt just works
Well sure, generally Blazor is Microsoft's answer to the popular JavaScript SPA frameworks. I have to say I'm very impressed with Blazor's consistent progress. Its going to be exciting to see future advancements in Blazor.
1. Next js is more than react, next js is react + nodejs + all the integration pieces required to get them to play well together. You do not need to add any dependencies to your next project to have a back end. Also, with the advent of react server components, more of your code is going to be running on a server by default. 2. Even though next js is only a subset of react, very few large companies are choosing react by itself over next js these days. The lines between the meta react team and the vercel next js team are blurring more and more. Just because blazor and next users are both a subset of the larger ecosystems does not mean they are equal in number. For example, Next js powers about 2% of the top 1 million sites on the web, whereas blazor only powers 0.03%. Seems like a pretty good indicator that there are a lot more proficient next devs than proficient blazor devs. 3. If you have an app that needs complex dynamic routing, I would go with a traditional react spa, not next js. Next js is inherently page based, so trying to force an SPA model over top of it makes little sense Also, Most web developers dislike Microsoft at large. I am among that number. There are plenty of places that will laugh you out the door if you suggest using dotnet
Thanks for this comment - it was very interesting to read. It's great to get an opinion from someone that clearly chooses Next.JS and React over Blazor and .NET. I personally think Microsoft offer the best tools and frameworks for software development, but I also love technologies like React and Next.JS and appreciate that they are both super powerful technologies!
somewhat disagree with using in house expertise as a factor in comparing frameworks..... if my startup has knowledge of php, that doesn't by itself help me evaluate php vs another framework.... I think technical merit of each should be boundary of the comparison
Sure, such decisions can be nuanced but having in house knowledge can certainly cut costs and perhaps add momentum to a project. I do however take your point :)
A much needed video on topic. I hope this videos gains popularity.
Thanks so much! The video comparing Blazor to React seems to be more popular, I guess because React is so popular but actually the comparison between Blazor and Next.JS is a better comparison because React is just a library whereas Blazor and Next.Js are both full web development frameworks where one technology can be leveraged to build a full-stack web application :)
Thank you, Gavin. I believe Blazor will take a leading position in the coming years, especially it is supported by Microsoft. We look forward to seeing practical projects using the latest versions of Blazor.
Yes, I think you might be right! :) I know if I was going to build a professional full stack web application - I would choose Blazor, .NET and C# = especially with the new features and enhancements due to be released with .NET 8. We'll definitely look at practical examples using Blazor on .NET 8 in up coming videos. :)
Since my background is in C#, of course Blazor is the right choice.
Thank you Gavin!
You are very welcome! :) You can't go wrong with Blazor - and it's about to get way better with the release of .NET 8! :)
Blazor especially with ver8. Best of both worlds and the html interaction with c# seems easier to me than js. Developing with Blazor is fun and has a short learning curve. (especially if you know c# or typescript). Good video, thanks.
You are very welcome! :) I love this comment! Thank you!
Excellent video, Gavin Lon. I felt I was watching a documentary.
Hey Kolade!! Great to see you in the comments section of one of my videos (Kolade and I both work for @freeCodeCamp). Thank you for your super positive feedback! I hope you have a fantastic birthday!! All the best!
You should measure performance of both technologies. Next or Astro are obvious choice for e-commerce apps because of that crucial factor.
Great - that's a great suggestion Next vs Astro. Thank you!
My background is in JavaScript and I have worked more than 15 years in JavaScript.. but I always prefer statically typed language so I prefer C# and I love blazor. Top of that blazor is way easier to build web apps!
I'm getting a lot of positive feedback about Blazor and I'm glad you mentioned the advantage of using a statically typed language (this advantage should not be underestimated). I agree Blazor is fairly easy to learn, I also think C# is pretty easy to learn too. Great comment, thank you!
Excellent comparison. Currently next.js has edge. Going to explore Blazor. Are they finally rendered to ESModule in browser?
Thank you! :) I found this article on using ESModule in browser. www.codeconcisely.com/posts/nextjs-esm
@@GavinLon thanks.
Personally I find nextjs a joy to work with
Yes, I really love Next.JS too :)
NextJS do actually support dynamic routing, even React with react router dom supports that
Thank you :) I know that dynamic routing is supported but perhaps its not as easy to implement as in Blazor.
@@GavinLon it's super easy, especially with next 13 where you have layout components, but it was already easy with next 12 and earlier. You simply just have to create a folder with the name of the folder in brackets and that's it basically. Layouts are even inherited if you don't create one on the folder level.
Edit: one thing that is a little bit tricky with next is nested dynamic routes is a bit confusing because you create them in your pages folder structure it is a bit difficult to visualize, but it does not take much effort to understand it when you need to
Okay thanks for your comment. :) I should have been more clear in my first comment. I think it's probably not as clean or elegant (if you like) when it comes to larger more complex applications. This is just opinion and in some articles others have also expressed this but of course many developers like yourself may disagree with this assertion :)
choosing blazor over next is a huge lol
care to elaborate on that statement? In its last iteration, it does appear to do pretty much everything Next does :-)
@@unhandledexception1948 blazor is made for be developers who righteously don’t want to learn js frameworks for frontend. next is made for fe developers who doesn’t want to learn oop based c# to make an api. so the future is full stack development, you just need to decide what tools you’re going to use.
if you’re more comfy with c# it makes sense to go with blazor. other than that, next/nuxt just works
Аргументируй!?
Blazor vs Angular?
Definitely!! Thank you! :)
I feel like Blazor is trying to catch up with NextJS. And surely it has less samples and community inputs.
Well sure, generally Blazor is Microsoft's answer to the popular JavaScript SPA frameworks. I have to say I'm very impressed with Blazor's consistent progress. Its going to be exciting to see future advancements in Blazor.
1. Next js is more than react, next js is react + nodejs + all the integration pieces required to get them to play well together. You do not need to add any dependencies to your next project to have a back end. Also, with the advent of react server components, more of your code is going to be running on a server by default.
2. Even though next js is only a subset of react, very few large companies are choosing react by itself over next js these days. The lines between the meta react team and the vercel next js team are blurring more and more. Just because blazor and next users are both a subset of the larger ecosystems does not mean they are equal in number. For example, Next js powers about 2% of the top 1 million sites on the web, whereas blazor only powers 0.03%. Seems like a pretty good indicator that there are a lot more proficient next devs than proficient blazor devs.
3. If you have an app that needs complex dynamic routing, I would go with a traditional react spa, not next js. Next js is inherently page based, so trying to force an SPA model over top of it makes little sense
Also, Most web developers dislike Microsoft at large. I am among that number. There are plenty of places that will laugh you out the door if you suggest using dotnet
Thanks for this comment - it was very interesting to read. It's great to get an opinion from someone that clearly chooses Next.JS and React over Blazor and .NET. I personally think Microsoft offer the best tools and frameworks for software development, but I also love technologies like React and Next.JS and appreciate that they are both super powerful technologies!
Ignorance and tribalism at it's peak
Good video but not even Microsoft is using blazor 😂 Azure DevOps use react
This!
somewhat disagree with using in house expertise as a factor in comparing frameworks..... if my startup has knowledge of php, that doesn't by itself help me evaluate php vs another framework.... I think technical merit of each should be boundary of the comparison
Sure, such decisions can be nuanced but having in house knowledge can certainly cut costs and perhaps add momentum to a project. I do however take your point :)
Next is super fast framework for web application
Next is an excellent framework! :)
Everything is better than next js lol
Well I think Next.Js is a great web development framework - but my bias is of course toward Blazor.
Yeah, specially after NextJS 13
Microsoft comprehensive documentation?... lol
Yes, Microsoft Learn has some great learning material :)