3 ms·
I agree, which is why I referred to it as "google-chrome-ing" (very awkward term) in my original post. The Chrome teams (the ones that deal with standards, imp
by hardwaresofton 6y ago
I agree, which is why I referred to it as "google-chrome-ing" (very awkward term) in my original post.
The Chrome teams (the ones that deal with standards, improving chrome, etc) are certainly filled with good people trying to improve the web, but there is such a conflict of interest there with a more open web or a web with certain features. Those employees are obligated to be on the wrong side of those discussions in really insidious/subtle ways sometimes, and those at the level at which strategy is conducted have a clearer view but have an even stronger incentive.
- cycloptic 6y agoI don't see how this is related to what Chrome is doing. What Web APIs have been implemented in Chrome that are available as proprietary closed source only? Looking at Google's wiki, I do not see any APIs that are omitted from Chromium: https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md https://chromium.googlesource.com/chromium/src/+/master/docs...
- hansvm 6y agoDRM is a thorny issue. https://news.ycombinator.com/item?id=19553941 https://news.ycombinator.com/item?id=19553941