The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
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 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 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.
WebAssembly is the future - at least it is for me whenever I need to build client-side web app functionality.
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.
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...
Sr. Software Engineer
Black Falcon Software, Inc.
I encourage you to go back and read what the MSM wrote about him when he ran against Obama the first time. His "Bomb, Bomb Iran" comment. And the fact that amazingly, HE TOO has a "Foundation" that takes money from the likes of George Soros (a Devout Globalist, who has a stated goal of destroying America, and Capitalism, and a shameless Nazi supporter who said he lost no sleep over what he did).
Funny how the theme changes when he dies. My opinion of him will never change. As a libertarian, I view him as a war monger who profited from big military contractors.
Arthasastra: Book VI
The king who is situated anywhere immediately on the circumference of the conqueror's territory is termed the enemy.
The king who is likewise situated close to the enemy, but separated from the conqueror only by the enemy, is termed the friend.
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
That's the most honest thing I've read in this thread, and reflects the reality as I see it, and tried to state it. If he was Pro-Trump he would be demonized as a Nazi, Baby-Killer, SongBird, WarMonger. But like a TYPICAL Politician, he wanted good press in his dying days, so he went the other way. And "Look, all is forgotten!" LOL!
I wonder what are your strategies for learning a new technology. Do you read one or more books first to get a grasp of what a certain technology is capable for, or do you start developing or practicing creating apps after reading some articles and then googling the missing pieces along the way as you code? I know people who never read books cover to cover and just learn on the go.
I like to have a better grasp of the technology first before starting a project, so I try to read a beginner book first, then some intermediate to advanced books, sometimes before even trying to create an app. Sometimes I just try to have a big picture of all the capabilities of a certain technology before starting to code and just go back to a certain topic when I am about to code. It is sometimes a problem of learning to much firsts before starting coding.
If you try to go and immediately code after reading a few tutorials, you may be able to create a full app without entirely knowing the full capabilities of the technology, and so you may try to do certain things the wrong way when there are a more official way on doing it.
Let's put React.js for example. I can simply learn react by looking at the "Getting Started" and some basic concepts, and then start coding immediately. But then I will miss concepts like redux and other patterns if I don't read an entire book.
What are your thoughts? What is the better way to learn and be comfortable with a certain technology?