3 ms·
Hypothesis: this will always be true. Standards compliance doesn't guarantee implementation compatibility (because the standards basically never include impleme
by shadowgovt 6y ago
Hypothesis: this will always be true. Standards compliance doesn't guarantee implementation compatibility (because the standards basically never include implementation details or benchmark guarantees), so there will always be cost associated with full browser compatibility in the margins of feature interaction (especially for complicated sites).
If the Chrome hegemony breaks down, another hegemony will take its place.
- SilasX 6y agoI think it might not have been true if Mozilla hadn't been so poorly managed and sent Firefox on quixotic adventures instead of making it a better browser, without constant feature regressions and bugs involving global, privacy-compromising outages: https://news.ycombinator.com/item?id=19871989 https://news.ycombinator.com/item?id=19871989
- shadowgovt 6y agoI can imagine an alternate universe in which the hegemony favors Firefox. The key idea is: the system favors hegemony for someone. The incentives are 1. Most web developers are trying to maximize number of people who can see their site 2. Some browser (barring lock-ins) will have the plurality of users 3. Developers seeking to minimize costs will target the browser with the most users 4. The browser most developers target will be the one most likely to be able to access the most sites 3 and 4 create a positive feedback loop; outside of other forces, we'd assume a browser with any small margin advantage to asymptotically approach full market control over time.