to Netscape (20 July 2000) TWO YEARS AGO, when your market share was still high as a kite, you pledged to fully support fi ve key standards in the next version of your browser... At last you are talking about shipping product by the end of the year. Sounds great – except that it’s the wrong year.
to address its basic fl aws has made it appear that you still consider Navigator 4 viable. It is not. ... keeping your 4.0 browser on the market has forced developers to continue writing bad code in order to support it. If you fail now, the web will essentially belong to a single company. And for once, nobody will be able to blame them for “competing unfairly.” So please, for your own good, and the good of the web, deliver on your promises while Netscape 6 still has the chance to make a di ff erence.
later (2000) were rather disappointing, with many mid- level PCs of the time too slow to run the larger codebase At release, the browser was deemed too unstable for production use. Netscape 6 was facing new competition from Internet Explorer 6.0, released in the summer of 2001.
features... After introducing IE-only layout features such as scrolling marquees and colored table borders in earlier versions, Microsoft is now committed to the standards set by the World Wide Web Consortium. https://www.pcmag.com/archive/microsoft-internet-explorer-60-31190 13
new Internet Explorer release and left the web in a vacuum, with no one fi xing bugs and improving existing technology. When Microsoft woke up fi ve years later, it was already too late. https://dev.to/schepp/today-the-trident-era-ends-7k5
each new user who installs Firefox + Google Toolbar as a result of a referral link from one of their pages. https://www.cnet.com/news/privacy/a-dangerous-con fl ict-of-interest-between- fi refox-and-google/
to Tim Cook, wrote in 2013 “The reason we lost Safari on Windows is the same reason we are losing Safari on Mac. We didn’t innovate or enhance Safari….We had an amazing start and then stopped innovating… Look at Chrome. They put out releases at least every month while we basically do it once a year.” https://twitter.com/patrickmcgee_/status/1389632382244847623?lang=en
to browser performance.… Apple bans alternatives to its own browser engine on its mobile devices; a restriction that is unique to Apple. The CMA is concerned this severely limits the potential for rival browsers to di ff erentiate themselves from Safari (for example, on features such as speed and functionality) and limits Apple’s incentives to invest in its browser engine. This restriction also seriously inhibits the capability of web apps – apps that run on a browser rather than having to be individually downloaded – depriving consumers and businesses of the full bene fi ts of this innovative technology. https://www.gov.uk/government/news/cma-plans-market-investigation-into-mobile-browsers-and-cloud-gaming
or services higher than those of others (self-preferencing) • reuse private data collected during a service for the purposes of another service • establish unfair conditions for business users • pre-install certain software applications • require app developers to use certain services (e.g. payment systems or identity providers) in order to be listed in app stores
browser engine, which is responsible for key browser functionality such as speed, reliability and web compatibility. When gatekeepers operate and impose web browser engines, they are in a position to determine the functionality and standards that will apply not only to their own web browsers, but also to competing web browsers and, in turn, to web software applications.
their dependent business users to use any of the services provided together with, or in support of, core platform services by the gatekeeper itself as part of the provision of services or products by those business users gatekeepers should also be prohibited from requiring end users to use such services