@@MarcusHammarberg Here are the applauds 1:01:04 . Yes, Blazor is awesome, but Stephen did this talk last year, and he didn't add anything new now. I watched anyway, there was no opportunity for applause
Yes, after silverlight another windows/IE only tool. It's as if nobody ever learns from the past. Kicking open standards in the nuts is what MS did best for decades, now tries to tune down a bit only to release this proprietary abomination.
@@borstenpinsel These kinds of comments are from people that speak saltily without analyzing what is actually being done. WASM is the future and Blazor is a good thing, unlike silverlight and webforms.
Blazor is amazing. I am already using the Blazor server on one of my projects. To do C# code instead of relying everything on javascript is great and makes web development much easier.
I am an expert Javascript programmer who knows Angular, React, and Vue, and I am impressed by this. Too bad the average Javascript programmer out there will not see the light and acknowledge the superiority of Blazor and Web assembly approach
You must understand, MS is private organization and a using their technology is a lock-in. There is a reason why more neutral platforms dominate the net for the last 10+ years. This is also the reason why MS when OSS in the last years - to be competitive. I say this as a former C# developer.
Yes Blazor Hybrid and Blazor Native UI should both be done. This is what I wanted to do long ago in the early 90s. Please deliver both of these technologies. This was the point of Canvas Control Library that I invented in 2012. Really what should be done is the Web Browser needs to be refined as the container to just draw on. What is the HTML element? It is just a screen a 2d place to draw whatever you want. This implies that the Web Browser is a 2D screen again to draw whatever you want. What is a Window Manager, Windows and Controls? It is just to manage and enable drawing on the desktop GUI of an Operating System. Which means cut through all the layers of abstraction/indirection and do what I showed open-source of this in Canvas Control Library into the basic Web Browser. Change the Web Browser to do what Canvas Control Library does in Javascript. An OS GUI inside of Window on the OS's GUI is what I mean. Yes, Terminal Server (remote GUI desktop) already does this but add to it all the functionality of a Window Manager, Windows, Controls, etc. This is what I thought of in the early 90s when I saw Mosaic in the GMI (Kettering University) UNIX lab. This should have been done back then except that the average person's computer and bandwidth (yes 56k modems) did not support it back then.
New Blazor fanboy here. Uh what am I missing? Where are all the comments and praises? Am I just late to the party and everyone else already celebrated? Or is everyone still following along other javascript ToDo examples because the cool young kids are still using that sumthinsumthin.js framework? This is exciting stuff guys. High five!
Charles Rhee give them some time, they need it, and I don’t blame them, I would need it too if I had to figure out how to mix 100 libraries and 10 frameworks at the same time to fill up a data table
I think if they offer a grate PWA and fast crud development companies might start using it for the same reason asp.net forms did. But that was the same case as with Silverlight and that didn't work, I hope it gets some traction.
Love the talk. Have you a good way to do authentication on server-side Blazor? My goto auth for asp.net core is ASP.NET Core Identity, and I can’t get it to work with SS Blazor because of the SignalR connection (exception is thrown because the IP headers have already been sent).
Blazor can't replace JavaScript functionality on the web currently, we have invested thousands of hours and dollars to master JavaScript , and the supporting frameworks, like Vue, React, Angular. Also most of the web applications are using some JavaScript framework. I think Blazor is a premature for usage in the current time as it is highly server depended (as server application) which makes it slow compared to HTTP protocols or Ajax, and heavy on using browser caching in case of using web-sockets.
You don't have to use CSS directly though, if you don't want to. There are tool-kits such as BlazorStrap that allow you to use bootstrap CSS in your blazor project without ever touching a character off CSS code, you just use custom tags and attributes to style your UI. The idea behind blazor is component composition, so while you may have to use some CSS initially, the idea is that you will build up useful UI libraries that you can reuse, in much the same way you build up libraries of code you reuse. Once you've built something and actually added the CSS inside your component, you can then easily attach attributes to that CSS code so you never have to touch it again, and instead just let C# do the work. It's all rather wonderful really :-)
Please release all of them, I am really interested in Blazor Hybrid and B. + Native UI. In Blazor Hybrid it would be extremely cool if you easily could build a cross platform App running on *GNU/Linux* , Windows, Android(, iOS & Mac). Same for new Blazor + Native, but also please for Xamarin Forms + MvvmCross, GNU/Linux | e.g. GTK just is nearly always missing, it would be so cool if you would have a few options for doing all cross platform with .NET with a few clicks. Then C# and .NET would be one platform for nearly everything. My best dream would be the e.g. following: Open Visual Studio, create Blazor Cross-Platform project, configure UI framework to e.g. WebAssebly, or Native-UI or a mix, configure wanted platforms, like *Linux* , Windows, Android and so on, get a nice template like currently the Blazor template, maybe some more advanced examples in there to show more of what this is capable of or for easy editing, chose platform to start like Android simulator or e.g. Gnome 3 from WSL2 or just Windows, click run and it should work. :D ♥️ This would be soo cool. 👌😎 But it is already impressive work, good job. 👍
you can consolidate your Components into a Razor Class Library: docs.microsoft.com/en-us/aspnet/core/blazor/class-libraries?view=aspnetcore-3.1&tabs=visual-studio and use DI to hit the existing back end: docs.microsoft.com/en-us/aspnet/core/blazor/dependency-injection?view=aspnetcore-3.1#request-a-service-in-a-component
@@Leonardo0leandro0 Not just files, i want to separate hole front-end part. Is it possible, if for example i want to use another stack for the Back-End(for example node.js or e.t.c)?
@@DOTNETMAN Yes it is possible. You can use Blazor wasm just like an Angular/React SPA or stand-alone web app and call any kind of back-end using normal HTTP Rest calls or even gRPC-Web. I am prototyping a Blazor wasm app at work that calls both an ASP.NET back-end and Java Spring API
Is here someone who already uses this productively? I've heard from a developer who evaluated it for their company that it isn't ready enough yet and they'll use JS instead. But that opinion may be limited to his specific requirements. Any other experiences?
I have. There are some issues, but I would say there are more in JavaScript. I think the bigger problem than technology itself is finding the right structure for the files, for the code in the files.
It would be cool if you could provide a boilerplate as a state of the art with working with Blazor. .NET Developers are the type that want to know how things should be done. They are not passionate about the flexibility of the technology. That type of "artists" are in the javascript world. They are the ones who like to develop technologies, to complicate things and get nothing done. .NET Developers just want to create projects that are using the .NET Technologies. We like to hear "you should do it like this" and not "you can use it with Webassembly or with SignalR, it's up to you". It shouldn't be up to me. If switching to Blazor means I need to invest 1-2-3 weeks to make reverse engineering, to test if qRPC is a good idea or not, if to choose Webassembly or SignalR, to fix tons of configuration problems, then I rather stick with something I know already: React, Angular etc. Because I have already been through the headaches of choosing what is the best way of working with it, of configuring it, and so on.There is too much flexibility and negotiations on how things should be done. We don't need flexibility, we just need technologies to create the products we want to create. What if we would negotiate how programming languages work? You would get problems like: - changing to a different company/projects means learning the new programming language; - after using the language for 1 month, you realize your language cannot be generic, so you change everything. You refactor. After 3 monts you realize that it has some other dysfunctionalities because of the configurations you have chosen. Refactor...And that is exactly what is happening when technologies are being negotiated. We don't create low-level technologies, we just work with it. We don't want to do the research if qRPC is better than JSON or not. Just tell us which to pick.At this moment almost nobody is using Blazor because nothing is clear. Only the mongoDb-hippies are playing with it. But no serious company is attempting to use Blazor in a serious project that they want to create. And I think this is sad, because Blazor should be a real breakthrough. Please, just clarify the things. Make the default boilerplate. Set the rules. And let's get this going. Btw, a really nice presentation. Steve Sanderson is a really cool guy.
For those of you that hate C# or your company won’t jump on the Microsoft bandwagon, Nest.js is a great new backend framework that’s easy to work with and provides a lot of functionality like data validation and transforming to solve a lot of the problems that Blazor server attempts to solve. It looks and works a lot like angular, uses Typescript, and also supports gRPC along with many other microservices, runs in Node, and is 100% free and open source.
Blazor for me it wasn't secure , because you can steal code library from "xxx .com/_framework/blazor.boot.json" to download dll file , this made me very sad
Kudos for using WA, an open standard. Yay... But do you really need to create another web component standard? Seems to be like you would be in much greater gain if you could use native web components and give developers access to already made components and perhaps an open component directory, and the ability to share and improve. Or is Microsoft still anti-open-source and open standards?
Wow! Web technology is now 20 years behind innovation. All these things we where able to do in flash in seconds. Only language AS that destroy all! But because Steve Jobs new how horrible HTML5 and web technology was, Adobe and Apple destroy the web experience. Today we have to use many applications to create a horrible experience in building and deploying websites. There is NOT one single website today that works 100%. How about an app for that?
No... wrong, Webassembly is fast, it's the .NET framework runtime running on top of webassembly that is slow. What is fast if you use C++ or Rust to Webassembly. That is fast. Don't blame webassembly.
I think Microsoft is the most confused company in the world, I don't know the teams inside it work together or against each others. Blazor here can works native on mobile devices at the same time there is Xamarin you can make native mobile application with it , you want make server side application to make apis for your web/mobile/desktop apps you can do that with Blazor at the same time there is ASP.NET Core !!! I think Microsoft they must work on one Framework that works on all devices on any OS Like Google's Flutter (In Flutter you can make mobile/web application with it and very soon it will support desktop Windows,Linux and Mac OS and they plan to works on Chrome OS and Fushia OS the future OS from Google)
giving people option is not a bad thing and the folks working on xamarin and other mobile platform are different from the guys working on this. just because you are confused does not mean Microsoft is confused.
They are heading towards a single framework. Lot's of development going on currently and it's great to see. I get where you are coming from though. .NET Framework, .NET Core, Razor, Blazor Server, Blazor Client, etc. They are all integrating, but it's probably still not until version 6 that we'll see everything together
"why use vue, angular and react when we can use razor with an api" :)) the ui is terrible never modify an input width as you slideing . the web api and browsers not to mention older browser support is so important to support.
Comes with Dlls when you load a page. Very well polished turd from microsoft. Invest a few years in this until micro soft pulls the plug. Seems like ppl never learn their lessons
Silverlight can be run only on IE. WA is a new web browser standard and it's not forced by Microsoft. Blazor is UI framework that adopted a new platform.
@@strahinja1107 still not worth the transition. Plenty of code and experience in js and so, things are running smooth and perfect so no one got logic to scrap that and start over with Blazor!
@@yasser2768 , There are always projects where it doesn't make sense to completely rewrite them. That doesn't prevent new projects, or parts of existing projects from using new technologies.
@@yasser2768 This is a long game. Sure, in most cases you might not want to migrate, and so keep using your fave js framework. Looking forward, having the same strongly typed language full-stack such as C# as is the case here with asp.net core, it would be a compelling stack to invest in. The tooling, and commitment to open source lowers the cost and risk. Microsoft got this right and are heading in the right direction, IMHO.
The amount of effort he put into this presentation is amazing. Very good job
Stephen is a master presenter. Every time he blows me away!
Seriously - where are the applauds? He's just racking up amazeballz of demos and features and the audience is silent as a fishes... Why?! How?! Who?
@@MarcusHammarberg Here are the applauds 1:01:04 . Yes, Blazor is awesome, but Stephen did this talk last year, and he didn't add anything new now. I watched anyway, there was no opportunity for applause
He goes to quickly
Yeah he was terrific up there.
The Blazor Native stuff is amazing and is clearly the path forward. Microsoft, please productize this!
Many of these talks are frustrating hard to get through. This speaker wastes no time. Excellent work.
Blazing fast one might say
really good demo. finally something more advanced than "well the counter component.... counts"
Romeozor I mean it does count
It's like WPF/C# and HTML had a genius child.
No more JavaScript. Heaven!
Yes, after silverlight another windows/IE only tool. It's as if nobody ever learns from the past. Kicking open standards in the nuts is what MS did best for decades, now tries to tune down a bit only to release this proprietary abomination.
@@borstenpinsel - Web Assembly is an open standard.
@@borstenpinsel These kinds of comments are from people that speak saltily without analyzing what is actually being done. WASM is the future and Blazor is a good thing, unlike silverlight and webforms.
What’s wrong with Javascript / typescript?
@@SydneyWu It's typically slow because it's using the browsers engine to run instructions rather than the machine's resources.
We are starting our first large project using Blazor.
Is Blazor ready to production?
@@shogotube Yes.
Let me be more clear, server side blazor is.
So totally enjoyed the presentation! And you made it sound so do-able too! Thanks!
been waiting 10 years for something like this.
I don't get all of the naysayers in the comments. This is a great framework for people who work with .net regularly
Haters will always hate, and Microsoft haters will always look for any reason to Hate Microsoft.
Brilliant as always @StevenSanderson #StevenSandersonAtMicrosoft!!! Thanks a lot!!! ♥♥♥
I have to watched this many times to get the excited as many times.
Blazor is amazing. I am already using the Blazor server on one of my projects. To do C# code instead of relying everything on javascript is great and makes web development much easier.
Thanks a lot, this is the best I have seen so far on Blazor, gRPC and more
This guy is a genius. Excellent presentation.
What a great presentation! Exited about all features from the Blazor team. I hope I can try Blazor on production application ASAP.
Perfect! Can't wait to use it on my next project.
@26:19 talks about getting data from server to the client using Gspc
God bless you Steve Sanderson. Blazor is brilliant.
Excellent together with javascript service worker really robust.
Presentation is excellent too, alot of content covered with great examples.
Looks like good old days of RAD. Thank you!
Awesome video, long but clear. Thanks
We needed this 7 or 8 years ago - but, better late than never. :-)
Ah, such BETTER audio quality compared to NDC Sydney! Great talk!
Very nice and very helpful! Thank you for sharing this!
I am an expert Javascript programmer who knows Angular, React, and Vue, and I am impressed by this. Too bad the average Javascript programmer out there will not see the light and acknowledge the superiority of Blazor and Web assembly approach
You must understand, MS is private organization and a using their technology is a lock-in. There is a reason why more neutral platforms dominate the net for the last 10+ years. This is also the reason why MS when OSS in the last years - to be competitive. I say this as a former C# developer.
Михаил Найденов it used to be like this. But nowadays MS is way more open.
@@YourCRTube Things have changed since you stopped using C#. I advise you come back
Superb presentation; thank you !
Wow this is actually good.
Yes Blazor Hybrid and Blazor Native UI should both be done. This is what I wanted to do long ago in the early 90s. Please deliver both of these technologies. This was the point of Canvas Control Library that I invented in 2012. Really what should be done is the Web Browser needs to be refined as the container to just draw on. What is the HTML element? It is just a screen a 2d place to draw whatever you want. This implies that the Web Browser is a 2D screen again to draw whatever you want. What is a Window Manager, Windows and Controls? It is just to manage and enable drawing on the desktop GUI of an Operating System. Which means cut through all the layers of abstraction/indirection and do what I showed open-source of this in Canvas Control Library into the basic Web Browser. Change the Web Browser to do what Canvas Control Library does in Javascript. An OS GUI inside of Window on the OS's GUI is what I mean. Yes, Terminal Server (remote GUI desktop) already does this but add to it all the functionality of a Window Manager, Windows, Controls, etc. This is what I thought of in the early 90s when I saw Mosaic in the GMI (Kettering University) UNIX lab. This should have been done back then except that the average person's computer and bandwidth (yes 56k modems) did not support it back then.
Looks like Vue in c#
New Blazor fanboy here.
Uh what am I missing? Where are all the comments and praises? Am I just late to the party and everyone else already celebrated? Or is everyone still following along other javascript ToDo examples because the cool young kids are still using that sumthinsumthin.js framework?
This is exciting stuff guys. High five!
Charles Rhee give them some time, they need it, and I don’t blame them, I would need it too if I had to figure out how to mix 100 libraries and 10 frameworks at the same time to fill up a data table
@ minute 14:30 talks about the Bonus splitter
This is the future, and on top of that you can feel safer about your business logic when it's all in wasm
Its in MSIL, only the runtime is in WASM.
@@sinan720 There is AOT available for Blazor WASM today.
legendary presentation
C# is love ♥️
I need to create a pwa using blazor that can access the internal camera to read barcode and qrcode. Anyone has any article about this?
That's all great!
But how can you motivate companies or even small startups use it?
I think if they offer a grate PWA and fast crud development companies might start using it for the same reason asp.net forms did. But that was the same case as with Silverlight and that didn't work, I hope it gets some traction.
My clients already start using Blazor
@@FilipCordas Silverlight needed a browser plugin, like Java applets. Blazor doesn't need any add-ons.
This is so great!
Is there any place where I can get the source code of this example for testing in my machine?
Love the talk. Have you a good way to do authentication on server-side Blazor? My goto auth for asp.net core is ASP.NET Core Identity, and I can’t get it to work with SS Blazor because of the SignalR connection (exception is thrown because the IP headers have already been sent).
I want to know where can I download the sample code?
github.com/SteveSandersonMS/presentation-2020-01-NDCLondon
A browser based framework?! Add it to the pile!
Except it's not one more JS clusterfuck that forces you to learn a whole new of doing things.
Can we get the code for the Mobile App, it's not in the GitHub repo with the other samples.
Is it the React Native for the web's native JS
Sounds like a game changer.
Blazor can't replace JavaScript functionality on the web currently, we have invested thousands of hours and dollars to master JavaScript , and the supporting frameworks, like Vue, React, Angular.
Also most of the web applications are using some JavaScript framework.
I think Blazor is a premature for usage in the current time as it is highly server depended (as server application) which makes it slow compared to HTTP protocols or Ajax, and heavy on using browser caching in case of using web-sockets.
Hi! GreatFul!
But What About Type Script?
I don't really get it, what about the designing part still have to use css?
This is standard compliant, so of course yes.
You don't have to use CSS directly though, if you don't want to.
There are tool-kits such as BlazorStrap that allow you to use bootstrap CSS in your blazor project without ever touching a character off CSS code, you just use custom tags and attributes to style your UI.
The idea behind blazor is component composition, so while you may have to use some CSS initially, the idea is that you will build up useful UI libraries that you can reuse, in much the same way you build up libraries of code you reuse. Once you've built something and actually added the CSS inside your component, you can then easily attach attributes to that CSS code so you never have to touch it again, and instead just let C# do the work.
It's all rather wonderful really :-)
is this uploaded at 1.5 speed ? :D
Please release all of them, I am really interested in Blazor Hybrid and B. + Native UI.
In Blazor Hybrid it would be extremely cool if you easily could build a cross platform App running on *GNU/Linux* , Windows, Android(, iOS & Mac).
Same for new Blazor + Native, but also please for Xamarin Forms + MvvmCross, GNU/Linux | e.g. GTK just is nearly always missing, it would be so cool if you would have a few options for doing all cross platform with .NET with a few clicks.
Then C# and .NET would be one platform for nearly everything.
My best dream would be the e.g. following:
Open Visual Studio, create Blazor Cross-Platform project, configure UI framework to e.g. WebAssebly, or Native-UI or a mix, configure wanted platforms, like *Linux* , Windows, Android and so on, get a nice template like currently the Blazor template, maybe some more advanced examples in there to show more of what this is capable of or for easy editing, chose platform to start like Android simulator or e.g. Gnome 3 from WSL2 or just Windows, click run and it should work. :D ♥️
This would be soo cool. 👌😎
But it is already impressive work, good job. 👍
How could we separate the UI part(front-end) from Back-End, as we do in Asp.Net + Angular apps?
you can consolidate your Components into a Razor Class Library: docs.microsoft.com/en-us/aspnet/core/blazor/class-libraries?view=aspnetcore-3.1&tabs=visual-studio and use DI to hit the existing back end: docs.microsoft.com/en-us/aspnet/core/blazor/dependency-injection?view=aspnetcore-3.1#request-a-service-in-a-component
have your logic in separate files from your razor files. Like your own .cs files
@@Leonardo0leandro0 Not just files, i want to separate hole front-end part. Is it possible, if for example i want to use another stack for the Back-End(for example node.js or e.t.c)?
@@DOTNETMAN Yes it is possible. You can use Blazor wasm just like an Angular/React SPA or stand-alone web app and call any kind of back-end using normal HTTP Rest calls or even gRPC-Web. I am prototyping a Blazor wasm app at work that calls both an ASP.NET back-end and Java Spring API
@@DOTNETMAN I thought you meant in the same app. Yes you can have your static site and use any backend
Is the source code available for the application "Blazor Mart"
github.com/SteveSandersonMS/presentation-2020-01-NDCLondon/tree/master/demo/BlazorMart
@@jonwpayne thank you!
for the unappreciated Humor.. please know that you are funny Steve, yes you are.
I'll wait and see. As I have once fallen in Silverlight.
This isn't a plugin. This is open and standardized technology.
AWESOME!!!
What is .net? Is it a JS framework?
Can I develop .net on linux and then run .net app on linux in production?
You sure can
Is here someone who already uses this productively? I've heard from a developer who evaluated it for their company that it isn't ready enough yet and they'll use JS instead. But that opinion may be limited to his specific requirements. Any other experiences?
My clients already start using blazor
I have. There are some issues, but I would say there are more in JavaScript. I think the bigger problem than technology itself is finding the right structure for the files, for the code in the files.
Looks like a competitive for Flutter.
They aren't even in the same category, Flutter is a UI SDK, Blazor let's you build UIs using C# for interactivity where you would have used JS.
When they go fully native they have a ‘Silverlight feature complete’ situation.
Reinventing the wheel over and over.
I should have stayed with Delphi. Compile all to one exe. Cross platform.
It would be cool if you could provide a boilerplate as a state of the art with working with Blazor. .NET Developers are the type that want to know how things should be done. They are not passionate about the flexibility of the technology. That type of "artists" are in the javascript world. They are the ones who like to develop technologies, to complicate things and get nothing done. .NET Developers just want to create projects that are using the .NET Technologies. We like to hear "you should do it like this" and not "you can use it with Webassembly or with SignalR, it's up to you". It shouldn't be up to me. If switching to Blazor means I need to invest 1-2-3 weeks to make reverse engineering, to test if qRPC is a good idea or not, if to choose Webassembly or SignalR, to fix tons of configuration problems, then I rather stick with something I know already: React, Angular etc. Because I have already been through the headaches of choosing what is the best way of working with it, of configuring it, and so on.There is too much flexibility and negotiations on how things should be done. We don't need flexibility, we just need technologies to create the products we want to create. What if we would negotiate how programming languages work? You would get problems like:
- changing to a different company/projects means learning the new programming language;
- after using the language for 1 month, you realize your language cannot be generic, so you change everything. You refactor. After 3 monts you realize that it has some other dysfunctionalities because of the configurations you have chosen. Refactor...And that is exactly what is happening when technologies are being negotiated. We don't create low-level technologies, we just work with it. We don't want to do the research if qRPC is better than JSON or not. Just tell us which to pick.At this moment almost nobody is using Blazor because nothing is clear. Only the mongoDb-hippies are playing with it. But no serious company is attempting to use Blazor in a serious project that they want to create. And I think this is sad, because Blazor should be a real breakthrough.
Please, just clarify the things. Make the default boilerplate. Set the rules. And let's get this going.
Btw, a really nice presentation. Steve Sanderson is a really cool guy.
Im gonna learn c# first
Great
Excellent
Here's to the codes and slides, in case you're too lazy:
aka.ms/sanderson-london-2020
So unfortunate that any time was spent on server side and not just devoted all the Blazor dev time to client side. Everyone wants client side.
Oh man ... another technology which will last how long? Reinventing the wheel over and over again!
For those of you that hate C# or your company won’t jump on the Microsoft bandwagon, Nest.js is a great new backend framework that’s easy to work with and provides a lot of functionality like data validation and transforming to solve a lot of the problems that Blazor server attempts to solve. It looks and works a lot like angular, uses Typescript, and also supports gRPC along with many other microservices, runs in Node, and is 100% free and open source.
but...nobody hate C# :)
Still no progress...
Moving back to web forms.
Blazor for me it wasn't secure , because you can steal code library from "xxx .com/_framework/blazor.boot.json" to download dll file , this made me very sad
And it's slow as fk compared to other technologies that does NOT use a .net runtime.
Kudos for using WA, an open standard. Yay... But do you really need to create another web component standard? Seems to be like you would be in much greater gain if you could use native web components and give developers access to already made components and perhaps an open component directory, and the ability to share and improve. Or is Microsoft still anti-open-source and open standards?
browser based .net. :D
Wow! Web technology is now 20 years behind innovation. All these things we where able to do in flash in seconds. Only language AS that destroy all! But because Steve Jobs new how horrible HTML5 and web technology was, Adobe and Apple destroy the web experience. Today we have to use many applications to create a horrible experience in building and deploying websites. There is NOT one single website today that works 100%. How about an app for that?
Great ,another promising technology from Microsoft which will be abandoned in 2 or 3 years.
WebAssambly is SOOOOOO DAMN SLOW. nobody can create anything to run it at least like webpage. needs LOTS of improvements.
No... wrong, Webassembly is fast, it's the .NET framework runtime running on top of webassembly that is slow. What is fast if you use C++ or Rust to Webassembly. That is fast. Don't blame webassembly.
I think Microsoft is the most confused company in the world, I don't know the teams inside it work together or against each others. Blazor here can works native on mobile devices at the same time there is Xamarin you can make native mobile application with it , you want make server side application to make apis for your web/mobile/desktop apps you can do that with Blazor at the same time there is ASP.NET Core !!!
I think Microsoft they must work on one Framework that works on all devices on any OS Like Google's Flutter (In Flutter you can make mobile/web application with it and very soon it will support desktop Windows,Linux and Mac OS and they plan to works on Chrome OS and Fushia OS the future OS from Google)
giving people option is not a bad thing and the folks working on xamarin and other mobile platform are different from the guys working on this. just because you are confused does not mean Microsoft is confused.
They are heading towards a single framework. Lot's of development going on currently and it's great to see. I get where you are coming from though. .NET Framework, .NET Core, Razor, Blazor Server, Blazor Client, etc. They are all integrating, but it's probably still not until version 6 that we'll see everything together
Way too old and out dated approach
What's a more modern approach then?
Ziad Hatahet I want to know too, this is bleeding edge, I hope the answer isn’t Angular 25/Vue 4/React Pro Max
@@willinton06 i believe he is one of those linux people that is butt hurt at microsoft cause they think its cool
"why use vue, angular and react when we can use razor with an api" :)) the ui is terrible never modify an input width as you slideing . the web api and browsers not to mention older browser support is so important to support.
Oh my. Nobody wants .net on desktop and now it's coming to web?
On the web you won't know it's .net
.NET has been big on the web for at least a decade
Who's told you nobody wants .NET on desktop? What do you mean by .NET? The Framework, Runtime, Standard?
This is a very uninformed claim, hahaha
Comes with Dlls when you load a page. Very well polished turd from microsoft. Invest a few years in this until micro soft pulls the plug. Seems like ppl never learn their lessons
It's gonna fail like silverlight
Waste of time and brain
Silverlight can be run only on IE. WA is a new web browser standard and it's not forced by Microsoft. Blazor is UI framework that adopted a new platform.
It's miles different than Silverlight. And it's pretty nice.
We use it for work. We had an angular app, which we migrated to blazor.
@@strahinja1107 still not worth the transition. Plenty of code and experience in js and so, things are running smooth and perfect so no one got logic to scrap that and start over with Blazor!
@@yasser2768 ,
There are always projects where it doesn't make sense to completely rewrite them. That doesn't prevent new projects, or parts of existing projects from using new technologies.
@@yasser2768 This is a long game. Sure, in most cases you might not want to migrate, and so keep using your fave js framework. Looking forward, having the same strongly typed language full-stack such as C# as is the case here with asp.net core, it would be a compelling stack to invest in. The tooling, and commitment to open source lowers the cost and risk. Microsoft got this right and are heading in the right direction, IMHO.