> > Anything where I need to be clever (use the UI), is the desktop app that > connects with the API or database directly. > This means that my users have two UI's to deal with (what a pain). >
I also try to find a desktop solution where possible first. I would only fall back to server-side web app if there was no other choice, and I would people involved that the UI would be relatively dumb and it would take 10 times longers to create the finished app. After the way we were burnt by MS over Silverlight, I am being very slow > about going down the Blazor path now. > Like you, I burnt so much time, money and effort on Silverlight, not going > to try that again until I see strong community support. > (I thought I saw strong community support for Silverlight, so don't > trust my views on this). > Well, I don't really point the finger of blame at Microsoft directly. The platform for the Silverlight plug-in was pulled out from under everyone, including Microsoft. I'm not sure if their full power and influence could have saved Silverlight and everything that supported it on all platforms. I was more angry at the way it just dropped like a hot poo and was painted out of history (like people in those old group photos with Stalin). Our 15 year old serious SL5 app is almost replaced now with a Blazor app, but we had to buy lots of expensive Telerik and GrapeCity components to replace the right SL UI, and still it's nowhere near as good. I think the support for Webassembly and Blazor is strong enough now to make me feel comfortable. I've got one pretty serious app published now and I know people who have really big Blazor apps out there. I think the only Blazor-killer that might come along will be something really orthogonal and new that finally breaks us out of HTML5 in the browser. I'll be waiting... *Greg K*
