Is Blazor the next Silverlight
-
I love adopting new tech, jumping in early and spending weeks getting a handle on some new framework, tool set, paradigm or methodology. NOT I loathe the current web stack with it's myriad of javascript frameworks and have refused to have anything to do with it for LOB work. So I stumbled across the new Blazor framework from Microsoft, the presentation made it look simple, based in c#, build in VS and I don't need to deal with javascript to any great degree. However having waited 2 years for Silverlight to stabilise and then doing another 3-4 years of development only to have add in support withdrawn from browsers I not enamoured with getting into another web framework. Is there any confidence this framework will become accepted.
Never underestimate the power of human stupidity RAH
The death of silverlight was a pain, that I am still feeling but I think ultimately the right thing, plugins such as SL and Flash were a stop gap solution to the limitations of HTML at the time. HTML / JS / CSS are much richer now. However Blazor is just one implementation of Web Assembly aka webasm. see www.webassembly.org. webasm I think is here to stay as it's the logical next step. But, as previously said this is experimental, so should not be used in production code at the moment. So the question then becomes is Blazor worth trying, I would say yes, Steve Sanderson is the guy behind Knockout.js who is an MS employee and to me seems to be more of a developer's developer, rather than some of the self promoting media whores out there. Personally I am waiting for it to become production ready and will move my code over to it when this is the case.
-
I love adopting new tech, jumping in early and spending weeks getting a handle on some new framework, tool set, paradigm or methodology. NOT I loathe the current web stack with it's myriad of javascript frameworks and have refused to have anything to do with it for LOB work. So I stumbled across the new Blazor framework from Microsoft, the presentation made it look simple, based in c#, build in VS and I don't need to deal with javascript to any great degree. However having waited 2 years for Silverlight to stabilise and then doing another 3-4 years of development only to have add in support withdrawn from browsers I not enamoured with getting into another web framework. Is there any confidence this framework will become accepted.
Never underestimate the power of human stupidity RAH
Why is MS basing Blazor on .NET Mono, instead of .NET Core?
-
I love adopting new tech, jumping in early and spending weeks getting a handle on some new framework, tool set, paradigm or methodology. NOT I loathe the current web stack with it's myriad of javascript frameworks and have refused to have anything to do with it for LOB work. So I stumbled across the new Blazor framework from Microsoft, the presentation made it look simple, based in c#, build in VS and I don't need to deal with javascript to any great degree. However having waited 2 years for Silverlight to stabilise and then doing another 3-4 years of development only to have add in support withdrawn from browsers I not enamoured with getting into another web framework. Is there any confidence this framework will become accepted.
Never underestimate the power of human stupidity RAH
I have exactly the same hesitations. I also waited two years for Silverlight to stabilize, and jumped in, and wrote four applications that I now have to replace before the end of life for Silverlight. My understanding is that Blazor is different in that it is actually compliant with a web standard that is being supported in all browsers, including Safari. So what will happen is that everyone will adopt this new standard and support it up until Microsoft begins to dominate in the space at which point Java fanbois will tell managers to go with Java based solutions because... Java isn't Microsoft and even though every machine in the organization runs on Windows 10, the servers are all Windows, and everyone uses Office and Exchange - we'll adopt some application that uses Oracle (worst GUI ever) and a patchwork of Java frameworks, libraries, and pre-packaged nightmares and string it all together into a big ball of sh*t because if it is elegant and easy then it isn't IT. At least that is how we do stuff where I work.
-
Why is MS basing Blazor on .NET Mono, instead of .NET Core?
I am not an expert, but I think it is because mono is more portable than .net core. And I am sure MS would love to tell you they also "own" Mono (from when they bought Xamarin) and that it is part of the .net framework. Also blazor was originally created by Steve Sanderson as a personal project and then adopted by MS.
-
I love adopting new tech, jumping in early and spending weeks getting a handle on some new framework, tool set, paradigm or methodology. NOT I loathe the current web stack with it's myriad of javascript frameworks and have refused to have anything to do with it for LOB work. So I stumbled across the new Blazor framework from Microsoft, the presentation made it look simple, based in c#, build in VS and I don't need to deal with javascript to any great degree. However having waited 2 years for Silverlight to stabilise and then doing another 3-4 years of development only to have add in support withdrawn from browsers I not enamoured with getting into another web framework. Is there any confidence this framework will become accepted.
Never underestimate the power of human stupidity RAH
I've been under the impression over the past 4-5 years that Javascript is the new Silverlight. The perception I've always gotten is that their NodeJS investment and efforts are their way of placating the OSS community. What's really lousy is that there is no migration strategy to go from SL into something else. For those of us that despise Javascript, WebAssembly is our great compiled hope for the future. All the client-side acrobatics JS frameworks have done to bastardize HTML in the browser (looking at you, React framework) can be drastically minimized using...Razor pages. How sweet it is! WebAssembly is the future - at least it is for me whenever I need to build client-side web app functionality. Javascript frameworks (especially React) are quickly becoming the Web Services of HTML.
-
I love adopting new tech, jumping in early and spending weeks getting a handle on some new framework, tool set, paradigm or methodology. NOT I loathe the current web stack with it's myriad of javascript frameworks and have refused to have anything to do with it for LOB work. So I stumbled across the new Blazor framework from Microsoft, the presentation made it look simple, based in c#, build in VS and I don't need to deal with javascript to any great degree. However having waited 2 years for Silverlight to stabilise and then doing another 3-4 years of development only to have add in support withdrawn from browsers I not enamoured with getting into another web framework. Is there any confidence this framework will become accepted.
Never underestimate the power of human stupidity RAH
Though I have never been a fan of ASP.NET MVC, I believe the new Blazor software is a step in the right direction as it is beginning to return to some of the ease-of-use that made WebForms so successful while allowing developers to conform to the C# language on both the client and server sides of the equation. Like many developers, I have found JavaScript to be a complete headache to work with and the prevalence of the JavaScript Frameworks now available has made web development a nightmare. As a result, I stopped developing my projects for the web when I retired from corporate development in 2014. As WebForms drifts into obscurity, I don't see Microsoft suddenly dropping the Blazor Platform once it has been released for commercial development. If they did this, the company would have no web development standard to rely on. That being said, I see Blazor being refined into a more WebForms like environment that will return web development to the same ease-of-use paradigm that made such Microsoft tools so popular...
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
Wow. Support for .Net 2.0. Let's all take 5 giant steps back in time.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013.net CORE 2.0. BIG difference! As a side note I would not ask if Blazor is the new Silverlight. It's a totally different thing. Blazor is based on web standards, WebAssembly being the most important, whereas Silverlight was a proprietary browser plugin. The question is also a lot broader than Blazor, since it's really WebAssembly that is the interesting thing here. Blazor is just a framework to enable C# developers to utilize the power of webassembly. So yes, I strongly believe WebAssembly is the future. Especially for LOB applications. Public facing websites will probably be running with javascript for years to come, but real applications will be WebAssembly.
-
.net CORE 2.0. BIG difference! As a side note I would not ask if Blazor is the new Silverlight. It's a totally different thing. Blazor is based on web standards, WebAssembly being the most important, whereas Silverlight was a proprietary browser plugin. The question is also a lot broader than Blazor, since it's really WebAssembly that is the interesting thing here. Blazor is just a framework to enable C# developers to utilize the power of webassembly. So yes, I strongly believe WebAssembly is the future. Especially for LOB applications. Public facing websites will probably be running with javascript for years to come, but real applications will be WebAssembly.
I read that it used Mono - that is *NOT* .Net Core.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I read that it used Mono - that is *NOT* .Net Core.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Blazor: a technical introduction[^] Read the part Code sharing and netstandard I should have been more specific. Mono on WebAssembly currently support .netstandard 2.0 (or higher depending on release timeframes) Another interesting discussion here: Who is Blazor for Exactly? - Shawn Wildermuth[^]
-
Blazor: a technical introduction[^] Read the part Code sharing and netstandard I should have been more specific. Mono on WebAssembly currently support .netstandard 2.0 (or higher depending on release timeframes) Another interesting discussion here: Who is Blazor for Exactly? - Shawn Wildermuth[^]
Trygve333 wrote:
Another interesting discussion here
It's really not that interesting.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I love adopting new tech, jumping in early and spending weeks getting a handle on some new framework, tool set, paradigm or methodology. NOT I loathe the current web stack with it's myriad of javascript frameworks and have refused to have anything to do with it for LOB work. So I stumbled across the new Blazor framework from Microsoft, the presentation made it look simple, based in c#, build in VS and I don't need to deal with javascript to any great degree. However having waited 2 years for Silverlight to stabilise and then doing another 3-4 years of development only to have add in support withdrawn from browsers I not enamoured with getting into another web framework. Is there any confidence this framework will become accepted.
Never underestimate the power of human stupidity RAH
MS can revive Silverlight by reimplementing it in Blazor/Webassembly without use of plugin
