4 ms·
I would postulate that the cause of this is that, as a provider of services, Google kind of knows what's difficult to do in a browser and what apis are needed t
by Navarr 10y ago
I would postulate that the cause of this is that, as a provider of services, Google kind of knows what's difficult to do in a browser and what apis are needed to make it more native-like.
So it's not a terribly bad thing, unless other people's standards are just being ignored
- hobarrera 10y ago> So it's not a terribly bad thing, unless other people's standards are just being ignored. It's actually an unfair advantage. "Oh, let's standardize what Chrome already has implemented and Google is using". This immediately sets Firefox behind the new "standard", and website that don't work on FF technically "follow current standards".
- Manishearth 10y agoActually, no. Google is bound to have its own favorite frameworks (perhaps even in house), its own coding style, and in general its own way of doing things. Most large companies do. Google would end up creating APIs that are most suitable for their use cases and their frameworks. These need not be the best APIs for all.