I do get your point, Chrome is launching new APIs faster than the other guys can catch up. My issue is that the others guys had a lot of time to create the APIs Chrome is creating now and has created. When Chrome was focused on making the web better, these guys were working on making it more restrictive.
These seem like useful APIs. Mozilla seems against these due to security risk, but then why not work on a protocol that is safe? Bringing NFC, USB, and Bluetooth to the web is important in my opinion. Apple still doesn't let you connect a bluetooth device via WebKit, but guess what? You can pay to install a browser on the App Store that does.
Nothing is going to be perfect at the beginning but if Mozilla is so against it, the best response is a better product.
> When Chrome was focused on making the web better, these guys were working on making it more restrictive.
What the hell are you talking about? Safari and Firefox were building a better web long before Chrome even came onto the scene.
Safari precedes Chrome by 5 years.
Firefox precedes Chrome by 6 years.
They were both making the web better when IE6 held something like 99% of the market.
> Mozilla seems against these due to security risk, but then why not work on a protocol that is safe?
What the hell are you talking about? You want Mozilla to implement a new safe protocol to replace USB?
> but if Mozilla is so against it, the best response is a better product.
Yes, and both Mozilla and Safari are against WebUSB for one simple reason: they want a better product that doesn't compromise user security. But sure, why they don't just build one, right?
Chrome doesn't care and ships it anyway, and for some reason you're saying it's Google who are building a better product. No. They are building a product that's better for Google, first and foremost, and everyone else (including security, privacy, long-term health and sustainability of the web) be damned.
On https://webapicontroversy.com, I see these APIs that Chrome supports that clash with Mozilla:
Web Bluetooth API Web NFC API Web USB API
These seem like useful APIs. Mozilla seems against these due to security risk, but then why not work on a protocol that is safe? Bringing NFC, USB, and Bluetooth to the web is important in my opinion. Apple still doesn't let you connect a bluetooth device via WebKit, but guess what? You can pay to install a browser on the App Store that does.
Nothing is going to be perfect at the beginning but if Mozilla is so against it, the best response is a better product.