Blazor: Why 2024 Is The Year Of Blazor 🚀
Вставка
- Опубліковано 23 сер 2023
- I think 2024 is the year Blazor with C# hits the mainstream. Now is the time to embrace the next big thing in web development technology from Microsoft.
👨🏫 Self-Paced .NET Bootcamp Course (Includes FREE courses)
learn.coderfoundry.com/
🙌 Support the channel and become a channel member
/ @coderfoundry
📖 Buy the Book: Breaking the Code
geni.us/breakingthecode-davis
👕 Grab some CF merch
teespring.com/stores/coderfou...
🗣 Join us on Discord
/ discord
👓 Buy the blue light blocking glasses we use at CF. Pixel Eyewear Glasses ($5 off with coupon code CODERFOUNDRY)
www.pixeleyewear.com/?ref=jsF...
💻 How to get your first coding job
coderfoundry.com/jobroadmap
🎥 The equipment we use at Coder Foundry
kit.co/CoderFoundry
DISCLAIMER: This video and description may contain affiliate links, which means that if you click on one of the product links, we’ll receive a small commission. This helps support the channel and allows us to continue to make videos like this. Thank you for your support!
Blazor definitely a game-changer for me in the web dev space, for a couple years now. I never had a good dev experience with anything JS-related, so I'm very happy to be rid of it.
🙏🙌
We agree it is a game changer.
JS is not bad per-say, however some of the language constructs are far from what C# offers. That requires to be in two mindsets at the same time.
The video beautifully showcases Blazor's simplicity, especially highlighting its incorporation of input tags, which are crucial for interactive applications. The ability for the code to run on the server and directly access databases and services is indeed a powerful feature.
Reflecting on the prediction made eight months ago regarding Blazor's potential domination of the market, it's worth assessing its current standing.
As someone who has been deeply rooted in Microsoft technologies since the early 80s, I resonate with the anticipation surrounding Blazor. However, history has shown that Microsoft's strength in language, such as C#, and tools like Visual Studio, hasn't always translated into market domination. Previous frameworks like XML, WPF, WCF, WebForms, MVC, and Razor, despite their merits, haven't achieved the anticipated widespread adoption.
One critical aspect where Blazor could improve is in striking the right balance between automation and flexibility. For instance, maintaining the original input tags and onclick event would offer developers more control and familiarity. My suggestion would be to adopt a hybrid approach, where developers can seamlessly integrate traditional HTML elements with server-side functionality.
For instance, instead of introducing new syntax like , retaining with the "server." prefix could signify that certain attributes are solely for server-side use. This approach mitigates the learning curve associated with new binding mechanisms, akin to what was encountered with WPF.
Similarly, replacing @onclick="HandleSubmit" with onclick="codeBehind.MethodName();" allows for greater flexibility and compatibility with existing JavaScript frameworks. This approach not only simplifies integration with client-side logic but also promotes reusability of HTML components, a limitation often cited with Blazor.
Introducing server events like server.onvalidation and server.onupdate could further enhance Blazor's capabilities, enabling developers to handle server-side interactions more intuitively.
Lastly, granting the code-behind the ability to manipulate HTML components directly, akin to DOM manipulation in other UI frameworks, would streamline synchronization with the client and simplify development workflows.
In conclusion, while Blazor shows immense promise, there's room for refinement to ensure it meets the diverse needs of developers and achieves the market penetration predicted in the video.
I have been developing for about 14 years now and 12+ on web
Now I work on Blazor and I agree, It is super easy to build applications and It's super fast to deliver. So, I like blazor as today's world we need to minimize the complexity and delivery with minimum time with and it has to be cost effective too. So blazor wins all these.
Thanks for watching, bringing a real-world perspective.
@@CoderFoundry You are welcome. Appreciate your effoft to bring these to us.
Thanks for an awesome power packed overview of Blazor 2024!
Thanks Bobby!
Any time!
I noticed in the video what looks like bootstrap was being used. Are there any UI libraries available for blazor. Something more like vuetify or quasar (vue libraries)?
It's html and css for views. So we use bootstrap but you can use tailwind if desired. If you want components there are many component libraries like blazorise
I like the idea, Do you know what product from MS was/were made in Blazor?
Not sure, but we are building a product for release later this year built with blazor
Thanks for the video! I'd like to ask if this solution is available for download? I really like the look and feel as it's very nice. Thanks again!
Sorry, no, the mortgage calculator is not available. We did make the movie list available, as seen in the follow-up videos
Things I've done this year with Blazor (could be tempted to make a tutorial or two at popular request):
-full voice to text to chatGPT to speech synthesis, with animated svg character
-full SVG parameterization, allowing for complex animations of icons and characters, including smooth color changes, that scale losslessly to any size (this is Blazor's secret superpower that nobody fully understands yet, including MS devs!)
-timed live recording of audio with images to make a slideshow in just a couple minutes
Some of these things require some Javascript, because (for example) Blazor doesn't have built-in support yet for things like the MediaRecorder API, which you obviously will need if you want to record audio. But Interop is so trivially easy in Blazor that integrating Javascript is hardly a problem at all.
Nice!
I do like what Microsoft is doing with Blazor. What worries me is exactly what you said in your introduction. They use to create a new web framework (or for that matter a new database access one) every some years. small todo apps can be created with any framework out there. The real business huge applications need stability for years to come. Nobody wants to rewrite a 1 million lines application too often.
I agree that rewrites are decisions all companies have to make when to do it. Blazor is the latest version of asp.net and offers some compelling reasons to use the framework if you looking to migrate your project from an older framework.
Thank you . Can I get the code for that demo interest calculation application?
Regards,
It's not public, but we have another repo we made public. In our render mode series of youtube videos.
The github link for the blazor movie app is the description.
ua-cam.com/video/u4azTLLGt8U/v-deo.htmlsi=pOFMiizRKz-Pg_eW
I get it It's a new big thing but as a junior Developer that learning a lot of TypeScript things for the frontend {Angular} and Web API for the Backend do you really thing should I let go all of that and start Blazor immediately? or should I wait for now deeper my knowledge in technologies that I already learn this year?
Keep with what your learning if you're already a chunk in.
Is it still uses signalr for blazer SSR? Need to worry about scalability as well if web socket is involved
So the webassembly with auto mode is going to be the way to go. If you have super high traffic site. Build a web api backend and build your components to run client and server side. Give them the render mode of auto. First render will use signlarR and download to wasm in the background. After that all components run client side in wasm and communicate via http to web api. Fast and scalable, and quick startup.
@@CoderFoundry ohh i forgot about auto render mode. I will try it with my next project thanks.
It's new for .net 8
I find that most of the interactivity in web apps tends to be isolated to small single sections; most of the app is static and can be easily rendered on the server with MVC/Razor Pages. But for those small interactive parts, I wish I could "opt into" using Blazor for **just** that one little section. That way you get all of the simplicity of MVC/Razor pages but still have the ability for client-sided interactivity when you need it without bogging down the whole app with complexity.
You can. Blazor components can have independent render modes. Render modes are not tied to the page. Blazor is razor pages plus components. It is a game changer.
You also can use components in mvc / razor pages frameworks.
@@CoderFoundry wait really 🤯🤯🤯
Guess the docs aren’t up to day but what did I expect it’s still in pre release
We have video coming soon. That shows off server side rendering
This is the kind of videos I like
Glad you liked it
I just wish to have an visual studio interface to drag and drop nice ui componets and set props on it just like a desktop app WF in a future. In a while I will keep writring code or using framework to deal with. Any way so happy with Blazor.
Yeah, drag and drop html editors are great in theory. The industry has been trying to make them for 20 years. A cms does work, but it is combined with a predefined template.
Currently, this does not work well with custom apps. Knowing html and css is a hard requirement still.
Blazorise vs mudblazor or ? which one will you guys recommend?
We using blazorise on a product we are building. We are building the .net 8 curriculum right now. I am going to try to not use any component libraries in class. But we will see. I like Blazorise.
Hello. I am finding this difficult to understand. Previously we had to choose between Server & Web Assembly. Now Microsoft has introduced 3 new render modes. Server-Side Rendering, Stream Rendering, and Auto. Also, now we must choose between two Interactivity Locations. Here are my doubts.
In case I choose Global interactivity location and Server or Web Assembly interactivity type, shouldn’t we have the option to create an application in Server mode and then when I wish to scale the app, I could switch to Web Assembly. I know we may be able to do this in Auto mode.
In case I choose Auto interactivity type, can I use either Server or Web Assembly render mode.
With Per Page/Component, is the purpose to have one component work based on Signal R and another as Web Assembly. If not, then isn’t it better to just use the global mode.
I understand Stream Rendering. It uses the channel to first fetch the page and keeps the channel alive to then fetch the data.
Server-Side Rendering. I know that if I don’t mention any render mode for a page/component and globally, then my page/component is going to fall back to Server-Side Rendering. My question is, will I get interactivity (Button click, etc.).
I feel I am still in the dilemma of Server or Web Assembly and now render modes with .NET 8. This is so confusing probably not for you . I may be wrong in many ways. Please correct me. I am new to Blazor. I know this may be the wrong video to post my question/doubt. 👍
Auto is the render mode that you don't have choose. It will be interactive it runs with signalR initially the web assembly once the download is completed.
If you don't care about infertility the run it server side and it will behave like mvc.
The cool part? Is you select the render on a component by component basis. So static content is always fast and interactive content is interactive
Hello, Can you please do portfolio reviews please. Thank you.
We will.
Yup agreed, and I'm already riding the Blazor wave...
Awesome
Where can we find the source code. I am new to Blazor and started learning it. Please reply.
That project is not public, but we have a public repo for server modes at the coderfoundry public github. The link is in the description of the video below
ua-cam.com/video/u4azTLLGt8U/v-deo.htmlsi=-DCEX2v2W_h_cGxH
Been using Blazor for 4 years now. Built 5 full fledged applications on 3 different companies.
I really love how quick it is to develop. I'm so happy to being able to stay in the .NET ecosystem even for frontend.
Can blazor apps run on older browsers? Say android 4 browser and such
Yes, the blazor server mode would work. Wasm I would bet would not. Auto mode would handle this scenario.
Any preferences between Blazor sever versus web assembly?
Both in the same project works really well. But wasm with c# api if I had to pick one. The beauty of it is we don't have to.
I'm currently using Blazor (WASM specifically) and I love it, however (coming from AngularJs) in comparison, the developer experience in the IDE is pretty bad. I miss the days where you could put a beakpoint anywhere and inspect any property any time no matter how many 'dots' you go deep or have to worry the evaluation will eventually fail. If anyone can tell me how to avoid those issues in my setup I would very much appreciated it.
Just try the latest .8 version, vs studio 17.8 with .net 8 sdk. it's pretty cool and tons of improvements.
Looks like I came to coding just when the party's getting starting 🙂
I started when you either took over this channel way back in the day and i was deciding between going to your boot camp or dev mountain for ios (uikit days). I wished i would’ve gone to your bootcamp. I did get a job and a cs degree and said to myself whatever happened to that dotnet guy that had a school? 🤔 the algorithm gods sent me back to you 🤲🏾 😂. So i’m back. Learning C# once again after getting furloughed from a vuejs job in the DOD space and eager to learn. Will setup the alerts too. I went over dotnet 8 with c# 12, learned about Linq among other things and felt right at home. Anybody coming to this channel trust this guy in the video is the truth! wish covid wouldn’t had happened. Literally the only reason i went the ios route because the bootcamp made some crappy remote version and i finally paid off those $10k like two years ago. Got my popcorn ready, cs degree check, top secret clearance check, now just need the dotnet knowledge 🧠
The DX looks awesome. 8:29 Microsoft’s control there is a double edged sword. Those advantages exist, but on the flip side, you’re entirely reliant on them. Overall potentially not a that huge of a risk (since they aren’t Google, known for axing things at the drop of a hat). I’m not at all in the .NET ecosystem, just here to learn how it works architecturally, so super interested in learning more about how it works on the inside, like what runs where and precisely how. From what I can tell it’s WASM on the client side, so that’s interesting as well. Other Q’s crop up as well like how to best integrate with 3rd party JS and etc.
Js interop allows you to call into browser api and third-party libraries. One note is that blazor handles all of the dom manipulation, either the client side or the server side. Js would be used for something that does not exist like a charting or advanced grid. But many blazor libraries already exist that cover components that are not implemented by Microsoft.
I just started working as a software developer for a company and it's my first job. They want me to use Blazor. But I'm worried about finding a job after this company. What's your take on that?
Blazor is the flagship dev framework from Microsoft it will be in demand.
I'm using Node with Blazor just to piss off some people
In germany so many companies use java and i don't know why..
I like a lot of what Blazor stands for, but I'm worried that I'm going to need javascript tacked on to it to get everything done that I need to. The web is just so javascript dominant, it feels like a risk to stray from that. And if I just end up writing part C#, part javascript, I'd rather just use something more javascript-native. Mixing code styles is the devil.
It's worth a look for sure. Js interop is used when you have to call js. Many times, you do not need to.
Blazor works in conjunction with Razor.
Most of the people making negative comments about Blazor don't actually know anything about Blazor.
👍
I mean there is no particular advantage for Blazor over React though, meanwhile react has more mature ecosystem and frameworks like Next.js
I agreed 100% with you. Blazor to me is the best MS framework I have ever used. And I think its the future of MS development. Blazor was dream and now it's real. Blazor + MudBlazor can build any super professional applications. Thanks a lot for your great video.
Couldn't agree more!
2024 will be the year of Angular
That was last year. There is a new sheriff in town. 😀
I think Blazor is very well done and very good for department-level internal projects for Windows programmers. While I agree it may approach mainstream within the MS faithfull community, it's not ever gonna be substantially embraced by the larger Web dev community--and won't, by any measure, ever widely be considered "mainstream."
We can agree to disagree. But asp.net is already mainstream. This the latest version of asp.net This has nothing to do with windows or being windows developer.
This is a stark improvement over the current spa frameworks and will be widely adopted because asp.net is already widely adopted.
I don't understand how does Windows developers come into this. Or maybe you meant to say for C# programmers.?
@@CoderFoundry my blazor WASM application weighs 40MB, this is an awful lot for a real and high-quality Internet project, I rewrote everything to another framework and now it’s a couple of megabytes and full interactivity
What version of .NET did u use for that blazor app?@@minimalstory
For large apps. We are using a mix of render modes. It's super fast.
Blazor just adapted features from React which was present since ages ago.
Like server side rendering? I do think it is a component first framework, and the dom updating, templating with razor pages is next level. But yes, they both can update the page without a form post. Did they learn anything from react? Sure. But I believe they are bringing true innovation to the table.
Man I try install the whole package to code in BLAZOR and do some testing let me tell you the whole Microsoft C# and all that stuff is a pain in the ass I mean I do not know how you put a Video saying is going to be the future just to install the env it is crazy, in that time I can finish a Phone App running in windows Desktop, running in Linux Desktop, Running in Mac desktop, Running in web, Running in Android with flutter really sorry it is a waste of time, now when you have an error in C# is like you have to read a freaking bible of codes to see what the error means I'm really disappointed, plus the whole package is more thant 30GB WTF that's a STEAM game.
Installing visual studio? If you pick, every workload ot is large but pretty hands-off. For blazor all you need is web workload.
Looks like Coder Foundry didn't get the memo vendor lock-in is bad!
Blazor looks pretty cool but don't forget most of the ideas are taken from other frameworks. Blazor just feels like they are playing catch up rather than providing any innovation.
There are lots of frameworks for sure. But there are a lot of really great things about blazor.
@@CoderFoundryAgreed, just feels like they are always a couple of steps behind. For me Flutter for mobile and React / Electron for everything else are best in class toolsets.
Serve side rendering and integration with the dom is next level great. Whether over http or signlarR. Components are amazing. Orm and identity is built in. Not to mention c# and visual studio.
Yes and no, virtually anything on Microsoft websites/services runs on Blazor, as far as I'm concerned. They're still using React and React Native in a big way. Does this mean you shouldn't at least try to learn blazor? No, however, think about employability.
P.S: I love blazor.
It's okay to wish like that, but this is impossible. It's just another silverlight.
Except is not a plugin. It's based on standards. It is the next version of asp. It has already gained traction.
Looks great! Ms is just notoriously bad with documentation and examples
We will build lots of examples so you will how to use it. Follow our github and Learn.coderfoundry.com
I have been Microsoft software technologies for 30+ years. Is it just me or are microsoft web technologies getting increasingly more complex and less and less fun to use?
I think blazor is less complex than mvc. I believe it's easier to build with than react. But, web development over the years is more complex because of the demands of what a web application needs to do. It's not just Microsoft, but all the frameworks are complex.
I have the same understanding. Ms is going complex instead of simplicity. Hope this time its different.
Yeah, blame Microsoft for the increasing complexity of web app requirements
Flutter?
Do you believe mobile dev will supplant webdev?
The fact that its basically web forms for the kiddies in kinda laugable its only cause the kids dont no about web forms lol
Very little overlap with web forms. It's a component first framework. SignlaR and web assembly don't require a form for sending info to the server.
Two questions:
1. Will Coder Foundry be teaching Blazor 8?
2. With the explosion in mobile device development, what are the opportunities for employment in web development?
We will teach blazor .net 8 in 2024, it's not released until Nov 2023. It's currently in preview and the time of the recording august 2023.
Fullstack Web development is still the largest sector and most in demand job in development. So we are going to continue to teach that.
You can also build mobile apps with blazor components and C# using blazor Maui, no xaml required
The fact that MS owns it is a hard no.
What do you code with?
@@CoderFoundry you mean language and IDE?
Yeah just generally curious
What a dogmatic point of view. That's embarrasing for a developer.
With all due respect, I think you are dead wrong! Can't use Javascript frameworks nor libraries in Blazor nor has many of the browser issues has been fixed! I'll see you in early 2025 when I'll say, told you so!
Js interopt in blazor is a thing.
Depending on the render mode, like ssr, you can use any js framework you want. This is the new version of the asp.net framework. It's can be run total server side like mvc. Which can be paired with any js framework. It can run a signal R mode that allows for complex 2-way binding. Removes the need for a front-end js framework. It can also run completely on the client side in the web assembly. Which also negates the need for the js framework. Js libraries can be handled through js interopt if needed.
It's much more complete in the new version.
@@CoderFoundry I tried using Blazor client side implementation but I could not figure out how to use a JS library like React or Bootstrap and I couldn't find any tutorials on it making it look like all the UI styling would have to be done from scratch. That's a huge no-go for me!
So with web assembly you cannot use react. You can use bootstrap to style components. If you want to use react just use react with a webapi backend. If you want to use Blazor then use Blazor. Blazor in .net 8 is a front end framework and a serverside framework. Blazor will uses razor pages for the front end and web api for the backend. .NET 8 is bring both sides together.
So if you are interested in learning blazor we have a course go to learn.coderfoundry.com. We have the covers web assembly which uses bootstrap for styling. I am working on more videos for blazor for the youtube channel that will help you see what's coming for Blazor in 2024.
It has been used in production apps since 2 years. lol
@@obinnaokafor6252 Great! But doesn't mean the UI is modern nor beautiful for the consumer! Who wants to build an app where the UI looks 20 years old?
can i do .net in Mac os
Yes you can, either by VS Code plugin or Visual Studio for Mac, bear in mind that those alternatives are not as complete in terms of tooling as Visual Studio for Windows.
Jetbrains has a Mac product. I personally code on a Mac with Parallels to run windows. Modern m2 hardware while running windows. It's great.
@@CoffeeToCode11 VS for Mac has been canceled now it's VSCode and Rider