3 ms·
My point isn't from a "a single person should be able to build this" perspective. But from a "big players misuse this to grab market share" perspective. Like ho
by matsemann 5y ago
My point isn't from a "a single person should be able to build this" perspective. But from a "big players misuse this to grab market share" perspective. Like how youtube was slow in Firefox for years, since they used APIs only existing in Chrome. Others follow suit, and thus other browsers are forced to either implement the same thing (thus making it a "standard") or lose market share since stuff works better in other browsers.
- snet0 5y agoSure, this sucks. I guess the counterargument is that then, given that the new API in Chrome is an improvement over the standard, waiting for this API to be actually accepted and written into the spec is a long, arduous process during which Chrome is unable to implement an objective improvement to their user experience. My concern is basically that if we force browsers to be spec-compliant and wait for the due process concerning new features, we pump the brakes on everything, and we risk stalling genuinely beneficial updates.