Is Blazor the next Silverlight
-
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
