I look at how far we’ve come in the last twenty-plus years and in terms of application development productivity, you’d have to wonder what we’ve all been smoking.
*From:* [email protected] [mailto:[email protected]] *On Behalf Of *Greg Keogh *Sent:* Tuesday, 21 November 2017 9:17 AM *To:* ozDotNet <[email protected]> *Subject:* Re: Creating a browser-based product After the cluster fail that has been Javascript and Silverlight... I am NOT optimistic that anything will change in a positive way real soon. If you step way back and look at the last 25 years of the web, it's clear that the web browser should never have been used to run apps. First we had html in the dumb browser, which was only good for looking at cats and porn. Then someone decided to spice the browser experience up by knocking-up a script language without any proper research, design, conventions or consideration of the future. Then someone finally decided it was wise to pull the styling out of the markup to give us css. Then they made valiant attempts to run "real" apps inside the browser with Java applets, Flash and Silverlight. They all died for various reasons. Then we went back to using html, css and that stupid scripting language in an attempt to write useful apps. The browser, the rendering, the layout and the language all don't interoperate properly and there are no standards for developers to follow. This results in every bored academic and hobbyist writing their own framework. And here we are well into the 21st century with no robust way of creating an app in a web browser. *GK*
