3 ms·
Google's version of EEE is to churn the "standards" continuously by changing and adding to them rapidly to make it hard to even implement them, while also sprea
by userbinator 6y ago
Google's version of EEE is to churn the "standards" continuously by changing and adding to them rapidly to make it hard to even implement them, while also spreading widely the propaganda to cause developers to use the new parts --- even if not actually necessary. See all the static content sites turned into (increasingly often, Chrome-only) horrible SPAs.
There's a reason the word "deprecate" occurs so ridiculously often in the web development --- Google's weapon of monopoly is change: they are basically trying to outrun competitors. It's not Microsoft's proprietariness, but a brazenly open show of sheer power.
- scrollaway 6y agoOccam's razor, and my familiarity with the industry, both tell me it's not malicious but rather just various shades of incompetence & misaligned incentives that are producing such high amount of "spec churn". But if it were a strategy, "EEE" or "Embrace Extend Extinguish" is not a good term for it. Maybe call it EEEE. "Extend Extend Extend Extend".
- mattkevan 6y agoIn Google’s case it’s perhaps EELIE, embrace, extend, lose interest, extinguish.
- deleted 6y ago[deleted]
- toomim 6y ago> while also spreading widely the propaganda to cause developers to use the new parts --- even if not actually necessary There's a good argument to be made that WebHID is exactly that. There is already a HID API. This new one is just supposed to be "better" ... somehow... in some way... I'm not exactly sure what it is... but some googler on the internet says you should support it.