Earlier quoted context omitted.
Sorry, that’s just not what happened. I think there’s an important lesson in what happened to Mozilla, so I think it is worth clarifying. Chrome didn’t start from scratch (they used WebKit to start) and they didn’t overtake them overnight. Mozilla couldn’t decide what their focus should be for many years, and in that time Chrome grew thanks to Google’s infinite wallet. They made worthwhile risks that didn’t work out…
First, many years ago, they should have made an XUL IDE. Then they should have focused on XML and giving the world an XML based web-browser, trying to drive XML further. XML would have had a much better chance on the web, if web-servers could have responded to URL encoded XPaths (or even XQueries in POST/GET), serving back XML Fragments which could have been XMLIncluded by the browser. They could have lobbied that. N…
With computers having become faster, together with development thrown at it, that's not really an issue anymore, but developers have also realized these days that XML is far from human readable, and for the majority of applications it has been used for, simply a bad idea.