I've done one video so far on algorithms ruclips.net/video/v-soEokozdg/видео.html I'd certainly like to do more videos on data structures and algorithms! :)
I don't know about Blazor taking the lead if you are comparing it to some of the JavaScript based technologies. It will certainly gain in popularity and it is an excellent technology to learn. I would certainly recommend that all new .NET web applications be coded using the Blazor framework. It can pretty much do whatever MVC and Razor Pages can do and much more at this point.
I was new to C# and .Net (Core 3.1) in mid 2020. I tested Blazor at work but finally decides go with Razor pages as backend templating engine and Javascript/jQuery in the frontend. Blazor was buggy and to slow. In general Razor pages were also a nightmare due to long compile time after every single change in html templates etc. In the frontend there are so many hundreds and thousands of open source libraries written in Javascript, which can be easily integrated into every webpage build with html css javascript. In the era of microservice architected application software it easier develop nice apps in the frontend with JS and with any language in the backend. I do not think Blazor would beat JS frontend frameworks.
Thank you for your thoughtful comment :) Blazor is very different now to what it was in 2020. I personally would always consider React for the frontend, I do enjoy working with React and it does perform very well. I will always choose .NET for the backend. Blazor with .NET is very powerful, versatile (with features like for e.g. SSR, streaming rendering, and interactive auto render mode) and easy to work with and debug. It is especially great for an organisation that has predominantly C# and .NET skills. A team can develop an entire enterprise web application using .NET and C# on the frontend and backend with a minimal need for JavaScript code on the frontend. It's always a case of weighing up the pros and cons when choosing the technologies for the development of new applications. :)
Absolutely, Blazor is the future of .NET web development :) Please check out this video I did recently that may help you with structuring your learning progression with C# and .NET; ruclips.net/video/oTvg8vWCiKk/видео.html
@evelop3625 I meant specifically the future of .NET web development when compared to Razor pages or MVC. It is always important to know vanilla JavaScript and then if you know JavaScript, I recommend learning React as well.
@@evelop3625 I disagree. The future is webassembly and when WASM 2 comes out (100% DOM), browsers will become true VMs and javascript will not be able to compete with throughput, nor security. Unfortunately, for now, you still need javascript to load WASM code and do special graphics tricks (like using the canvas), kind of like when you needed Internet Explorer in the past to download better browsers.
@davestorm6718 Thank you for your thoughtful comment. I certainly think web assembly has the potential to make JavaScript less dominant in the future. There are of course a vast number of web applications that depend on JavaScript out there at present so realistically I think it'll take a very long time for web assembly to have a significant impact on the use of JavaScript. I certainly agree about the performance advantage provided through web assembly. Web assembly also allows for far better languages (like of course C#) to run within the browser, so that is a huge benefit for web development in general.
thanks blazor for making my life easier every single day.
my sleeping nights got improved after the easy life it gave me. 😌
Blazor definitely makes life a lot easier for us developers :) I really love how easy it is to test and debug code in Blazor!
please make a course on data structures and algorithms in C#
I've done one video so far on algorithms
ruclips.net/video/v-soEokozdg/видео.html
I'd certainly like to do more videos on data structures and algorithms! :)
Thank you Gavin,
Do you think the Blazor framework will take the lead one day? When do you expect that?
I don't know about Blazor taking the lead if you are comparing it to some of the JavaScript based technologies. It will certainly gain in popularity and it is an excellent technology to learn. I would certainly recommend that all new .NET web applications be coded using the Blazor framework. It can pretty much do whatever MVC and Razor Pages can do and much more at this point.
I was new to C# and .Net (Core 3.1) in mid 2020. I tested Blazor at work but finally decides go with Razor pages as backend templating engine and Javascript/jQuery in the frontend. Blazor was buggy and to slow. In general Razor pages were also a nightmare due to long compile time after every single change in html templates etc.
In the frontend there are so many hundreds and thousands of open source libraries written in Javascript, which can be easily integrated into every webpage build with html css javascript.
In the era of microservice architected application software it easier develop nice apps in the frontend with JS and with any language in the backend.
I do not think Blazor would beat JS frontend frameworks.
Thank you for your thoughtful comment :) Blazor is very different now to what it was in 2020. I personally would always consider React for the frontend, I do enjoy working with React and it does perform very well. I will always choose .NET for the backend. Blazor with .NET is very powerful, versatile (with features like for e.g. SSR, streaming rendering, and interactive auto render mode) and easy to work with and debug. It is especially great for an organisation that has predominantly C# and .NET skills. A team can develop an entire enterprise web application using .NET and C# on the frontend and backend with a minimal need for JavaScript code on the frontend. It's always a case of weighing up the pros and cons when choosing the technologies for the development of new applications. :)
JQuery in 2024? Seriously?!
signalR uses websockets under the hood right?
SignalR uses WebSocket transport where available and falls back to older transports where necessary :)
Hey Gavin, is Blazor worth to learn? Im a jr dotnet dev btw.
Absolutely, Blazor is the future of .NET web development :) Please check out this video I did recently that may help you with structuring your learning progression with C# and .NET;
ruclips.net/video/oTvg8vWCiKk/видео.html
The future is not Blazor, unfortunately the present and the future will be React, Angular or any other JS based framework.@@GavinLon
@evelop3625 I meant specifically the future of .NET web development when compared to Razor pages or MVC. It is always important to know vanilla JavaScript and then if you know JavaScript, I recommend learning React as well.
@@evelop3625 I disagree. The future is webassembly and when WASM 2 comes out (100% DOM), browsers will become true VMs and javascript will not be able to compete with throughput, nor security. Unfortunately, for now, you still need javascript to load WASM code and do special graphics tricks (like using the canvas), kind of like when you needed Internet Explorer in the past to download better browsers.
@davestorm6718 Thank you for your thoughtful comment. I certainly think web assembly has the potential to make JavaScript less dominant in the future. There are of course a vast number of web applications that depend on JavaScript out there at present so realistically I think it'll take a very long time for web assembly to have a significant impact on the use of JavaScript. I certainly agree about the performance advantage provided through web assembly. Web assembly also allows for far better languages (like of course C#) to run within the browser, so that is a huge benefit for web development in general.