Hi Greg K,
>From our conversations in late May updated, no I am not using Blazor yet, but... My feeling is still very negative towards the whole front end development situation. If your favourite language is C#, then Web Assembly and Blazer offers some real promise. Looking at the major releases: # Date Days ago Delta Link 0-5-0 25-Jul 11 48 https://blogs.msdn.microsoft.com/webdev/2018/07/25/blazor-0-5-0-experimental-release-now-available/ 0-4-0 7-Jun 59 36 https://blogs.msdn.microsoft.com/webdev/2018/06/07/blazor-0-4-0-experimental-release-now-available/ 0-3-0 2-May 95 15 https://blogs.msdn.microsoft.com/webdev/2018/05/02/blazor-0-3-0-experimental-release-now-available/ 0-2-0 17-Apr 110 70 https://blogs.msdn.microsoft.com/webdev/2018/04/17/blazor-0-2-0-release-now-available/ 0-1-0 ??? 6-Feb 180 https://blogs.msdn.microsoft.com/webdev/2018/02/06/blazor-experimental-project/ >From release 1 to 2 took 70 days, which is fair enough. The next release was 15 days later, then 36, 48 days apart. I am seeing a pattern here, the inter release gap is growing! That can mean many things, but in a vacuum of other information I am left guessing… it could be: 1. The project has lost momentum 2. The project is out of control and they are breaking features as they add new features, so it is taking more time to clean up between each release 3. The project is maturing and the releases are now just minor refinements 4. Other For me, I am thinking that 2 or 4 is likely to be the truth… It is clearly not 3, or there would have been a version 1 release. If you look at https://github.com/aspnet/Blazor/commits/master You see the last commit was yesterday... There are commits every few days from a mix of people So the project is still current Also worthwhile to read: https://github.com/aspnet/Blazor/wiki/FAQ There have been some recent articles on Code Project for Blazor: https://www.codeproject.com/Articles/1254687/Lets-learn-to-make-Shopping-Cart-using-ASP-NET-Cor https://www.codeproject.com/Articles/1254712/Music-Notation-in-Blazor-Part-2 https://www.codeproject.com/Articles/1251603/ASP-NET-Core-Blazor-Master-Detail-CRUD-with-Filter Updated Greg Harris’ current personal opinion: · If Microsoft does this right (not willing to comment on that) · If it remains open source · After it gets a little more mature. · After Microsoft (or other large company) makes a public commitment to the technology · If it works as expected I may change my attitude to the technology to support it In summary… Blazor looks like it could be a great technology, but after the right @#$%^&* up that was Silverlight where Microsoft #$%^&* us after building a great product, I am going to wait a little longer before I jump to another new product. My gut tells me that I should make the jump to Blazor. But my head continues to say wait and see... This opinion is supported by the inter release gap growing and a lack of public commitment from MS. If I had a current project that needed a strong front end, I may rethink this a little. All the best Just another Greg in the room :-) Greg Harris [email protected] phone: 0407 942 982 Baulkham Hills NSW 2153 On Sat, Aug 4, 2018 at 4:36 PM Greg Keogh <[email protected]> wrote: > Has anyone done anything useful with Blazor? Does anyone think it will > become useful for writing serious client-side web apps? > > I ask because I spent the whole afternoon stuffing around with it. After > bumbling around installing and uninstalling different Core and Standard > SDKs and Runtimes, and installing a VS2017 extension, I managed (after a > lot of hassle) to get the demo running. > > Then I noticed I had 10 different runtimes installed so I uninstalled the > ones I thought were older version near-duplicates. That broke my Blazor > development for ever more. I have tried to reinstall and reconstruct the > environment I had earlier when the demo worked, but I've only partly > succeeded. Now the demo runs, but dies with a generic app failed message. > I'm completely stuck there now. > > That aside, I'm disappointed that the resulting app is still based upon > html, css and JavaScript. It's unclear just how JS is being used in the mix > and what role it's playing. So despite the promises of Wasm with Blazor, > we're going to spend the next decade continuing to try to cobble together > UIs with top quality appearance and behaviour in html, css and scripts in > web browsers, and Wasm does nothing to help get us out of this > browser-based quagmire … pull the other one! > > Or do I misunderstand the architecture and Wasm makes better promises that > I haven't seen yet? Now I realise just how much I miss writing "real" apps > with XAML in Silverlight. > > *Greg K* >
