3 ms·

One thing I would add is constantly pushing the web standards forward with little regard to other players. They are adding features so fast that only the bigges

by yoz-y 9y ago

One thing I would add is constantly pushing the web standards forward with little regard to other players. They are adding features so fast that only the biggest structures can keep up. Many of these seem to exist just so ChromeOS can actually be considered a real OS. Writing a secure and up to date HTML rendering engine from ground up is now almost impossible (kudos to Mozilla to actually doing that).

zzzcpan 9y ago
Yeah, web standards and the whole Chrome browser is a prime example of embrace, extend, extinguish strategy from Google.
- oscargrouch 9y ago
  In the case of browser it would become: embrace, extend til no one else can keep up without expending a lot on it, kill competitors that do not have the pockets to follow up and monopolize
gcp 9y ago
The problem is that they push "standards" but the implementation of the standards often does not function as written. Typically standard bodies avoid this by requiring two independent implementations, but the market situation really means that the standard is what Chrome implements, and nothing else.
- romanovcode 9y ago
  They also ignore many things they push.
dontchooseanick 9y ago
Have you noticed how <custom-elements />, see https://en.m.wikipedia.org/wiki/Web_Components https://en.m.wikipedia.org/wiki/Web_Components, have become google web fundamentals, see https://developers.google.com/web/fundamentals/web-components/customelements https://developers.google.com/web/fundamentals/web-component.... Nobody discusses v1 vs v2, x-tags vs webcomponents polyfills even though mozilla had it right (all-in-one js vs typed sub-sections like shadow DOM) Having worked on both XMPP and CustomElements I couldn't agree more. Gosh, I've even already written on the quasi-impossibility to use Android as a non-google open-source system, see https://news.ycombinator.com/item?id=14516538&p=2#14526788 https://news.ycombinator.com/item?id=14516538&p=2#14526788 So kudos to Mozilla once again, they're the one pushing real FOSS

by yoz-y 9y ago

zzzcpan 9y ago

Yeah, web standards and the whole Chrome browser is a prime example of embrace, extend, extinguish strategy from Google.

oscargrouch 9y ago
In the case of browser it would become: embrace, extend til no one else can keep up without expending a lot on it, kill competitors that do not have the pockets to follow up and monopolize

gcp 9y ago

The problem is that they push "standards" but the implementation of the standards often does not function as written. Typically standard bodies avoid this by requiring two independent implementations, but the market situation really means that the standard is what Chrome implements, and nothing else.

romanovcode 9y ago
They also ignore many things they push.

dontchooseanick 9y ago

Have you noticed how <custom-elements />, see https://en.m.wikipedia.org/wiki/Web_Components https://en.m.wikipedia.org/wiki/Web_Components, have become google web fundamentals, see https://developers.google.com/web/fundamentals/web-components/customelements https://developers.google.com/web/fundamentals/web-component.... Nobody discusses v1 vs v2, x-tags vs webcomponents polyfills even though mozilla had it right (all-in-one js vs typed sub-sections like shadow DOM) Having worked on both XMPP and CustomElements I couldn't agree more. Gosh, I've even already written on the quasi-impossibility to use Android as a non-google open-source system, see https://news.ycombinator.com/item?id=14516538&p=2#14526788 https://news.ycombinator.com/item?id=14516538&p=2#14526788 So kudos to Mozilla once again, they're the one pushing real FOSS