7 ms·
...the rest should probably be considered "Chrome APIs" rather than "web APIs". That's just plain wrong. They're web APIs that are maintained by the W3C (in va
by onion2k 6y ago
...the rest should probably be considered "Chrome APIs" rather than "web APIs".
That's just plain wrong. They're web APIs that are maintained by the W3C (in various states) that Firefox doesn't support yet. That doesn't make them "Chrome APIs" just as a W3C spec that only Firefox supports isn't a "Firefox API".
Clipboard API: https://w3c.github.io/clipboard-apis/ https://w3c.github.io/clipboard-apis/
Battery API: https://w3c.github.io/battery/ https://w3c.github.io/battery/
Performance: https://www.w3.org/TR/resource-timing/ https://www.w3.org/TR/resource-timing/
Bluetooth API: https://webbluetoothcg.github.io/web-bluetooth/ https://webbluetoothcg.github.io/web-bluetooth/
The fact there isn't good cross-browser support is a reason to check whether or not a user's browser has support and use progressive enhancement to only show the feature to users who can benefit from it. It isn't a reason to avoid using the API unless you want to stick to the lowest common denominator for your users. In my case that would mean serving Chrome and Firefox users content that's developed for IE10. That would suck for people who are able to update their browser, so I prefer to put the effort in to adding features progressively.
- userbinator 6y agoGoogle essentially controls the W3C now.
- tasogare 6y agoThey also develop the browser that has the sheer majority of users and fund almost exclusively the only real technical competitor. This is really worrying.
- Spivak 6y agoSafari? And just because MS is rebasing on Chromium doesn’t mean they still don’t have a lot of technical might to throw at Edgeium.
- josteink 6y ago> That's just plain wrong. In theory yes, in practice no. If code doesn't run in 1 of 2 the browser-engines we currently have, I would consider that a major short-coming preventing me from using it in production.
- DarthGhandi 6y agoHow many of your production end users are using firefox? Low single digits?
- josteink 6y agoI am using Firefox, and I find that attitude among developers infuriating. If not enough users are using a platform, let's actively sabotage for that platform by making it less viable, further justifying your own laziness? Is that it? As someone who has gone from Amiga, to Mac, to Windows PCs, to FreeBSD and now Linux (not to mention the smart-phone story!), I take pride in my work being portable and cross-platform friendly. I have absolutely no desire to go back to the mono-culture days of MSIE. If you put it on the web, it should work everywhere, otherwise you're just being lazy and/or incompetent.
- deleted 6y ago[deleted]
- tssva 6y agoBeing portable and cross-platform doesn't mean you can't take advantage of things unique to a subset of platforms to provide a better user experience on those platforms. You just need to check for support and provide fallback on those platforms without support. One could easily argue that just using the lowest common denominator across platforms is in fact the lazy and/or incompetent option. Also you mentioned in another comment there being 2 browser-engines. There are in fact 3 major browser-engines.
- josteink 6y ago> Also you mentioned in another comment there being 2 browser-engines. There are in fact 3 major browser-engines. Fair enough. I was thinking in terms of browser-engine families (WebKit-based, Gecko-based) and tried to keep things simple, because I didn't want to overcomplicate my comment. You're right though that there's Google WebKit (Blink) and straight WebKit and that does make a difference which matters in this context.
- theli0nheart 6y ago[deleted]
- onion2k 6y agoThe authors aren't listed in the spec. You're looking at the editors. Anyone can contribute to the spec, and lots of people from Mozilla do. Taking the first one as an example, https://github.com/w3c/clipboard-apis/graphs/contributors https://github.com/w3c/clipboard-apis/graphs/contributors, marcoscaceres, janiceshiu, and Johanna-hub are current or former Mozilla staff, and plenty more who don't say one way or the other on their profile.
- gardaani 6y agoMozilla and Apple have publicly announced that they will not implement the Bluetooth and Battery APIs [1][2], which makes them definitely Chrome proprietary APIs. These kind of proprietary APIs are exactly what Microsoft did 10-20 years ago as part of their "embrace, extend and exterminate" process. They extended IE with their proprietary APIs (such as HTML+TIME), which other browsers never implemented. Bluetooth, Battery and many other Chrome APIs are just Google's and Microsoft's new attempt to "embrace, extend and exterminate" other browsers. [1] https://www.zdnet.com/article/apple-declined-to-implement-16-web-apis-in-safari-due-to-privacy-concerns/ https://www.zdnet.com/article/apple-declined-to-implement-16... [2] https://mozilla.github.io/standards-positions/ https://mozilla.github.io/standards-positions/
- deleted 6y ago[deleted]
- onion2k 6y agoMozilla and Apple have publicly announced that they will not implement the Bluetooth and Battery APIs [1][2], which makes them definitely Chrome proprietary APIs. I realise this is a bit pedantic, but this is wrong. They're W3C specs that Mozilla and Apple have chosen not to support. Calling them "Chrome proprietary APIs" is loaded with unnecessary and unhelpful subtext.
- realityking 6y agoIf we really want to be pedantic, then I must point out that they're not W3C standards and likely never will be. - Battery Status API was on a standards track but the last published version is a Candidate Recommendation from 2016 - Web Bluetooth is just a Community Group Draft. It's not even formally adopted by a Working Group. Neither is likely to progress to Recommendation status as the W3C - IMHO, wisely - requires to independent implementations before a specification is adopted as a web standard.
- tssva 6y agoIf we really want to be pedantic the post your comment refers to never said they were W3C standards. It referred to them as W3C specs which since they are api specifications and published by the W3C is accurate even if they are not standards.
- danShumway 6y ago> that Firefox doesn't support yet. > This specification was published by the Web Bluetooth Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. It's not a Chrome API because nobody else supports it yet, it's a Chrome API because nobody other than Chrome is going to support it. Ideally, Chrome itself should remove their implementation. The Web Bluetooth debacle is a good example of why new browser APIs shouldn't be turned on for end users by default until after they get far enough in the standards process that they we know they're not going to be rejected.
- Phrodo_00 6y agoThat "(in various states)" is very important. They're all drafts except for the performance API which is an RC. The four also seem really fit for fingerprinting. We don't need the web to have all the capabilities of a regular application.