Sure, deploying a web app to a server is easier than distributing thick client updates to many recipients, but that's a lucky side-effect. I stand by my claim that the web browser is a woefully inadequate host for business applications. I even have an example from today ...
A Blazor app version update was published, with some small fixes and UI tweaks which required css changes. I get a report that some clients are seeing parts of the page squashed or the text is ugly mixed sizes. After some back-and-forth with suggested quick fixes, the only fix was to clear the browser cache and restart the browser, which is really irritating for non-technical clients. I'm sure there are ways around this problem, with special meta tags or similar tricks, but it's more hoops to jump through and a good example of just how crappy the web browser is for business use.
-- Greg
I must end on a sad note.
ASP.NET, Blazor, JS, or whatever, all finish-up rendering in a web browser. It's tragic that the ancient dumb web browser is now the only host for web apps, and that we must attempt to present serious business applications using HTML, CSS and JS. The web browser was invented so we could have flame wars and look at pictures of cats and porn, it's barely evolved since then and it's completely inadequate for rendering business applications. Sure it can, but look at the flaming hoops and all the weird quirks you have to jump through. Web development is in a lamentable state.
You have a short memory of what it was like deploying apps back when thick clients were the only option. Modern web has done more to streamline ops than anything else and reduced application deployment to pushing code to an app service and end-user deployment to pasting a link in an e-mail or IM.
ozdotnet mailing list
To manage your subscription, access archives: https://codify.mailman3.com/