4 ms·
Funny thing is, they didn't stop it because it was Bad, but because some ppl at Google didn't want it. (probably because it was Bad, but it's sad to See that o
by k__ 10y ago
Funny thing is, they didn't stop it because it was Bad, but because some ppl at Google didn't want it.
(probably because it was Bad, but it's sad to See that one company has so mich power)
- cloverich 10y agoBased on the comments in the linked thread, its sounds as if all participating companies have that same veto power. The justification seems to favor filtering false positives over false negatives in a sense. I suppose I can agree with that.
- k__ 10y agoYes. Getting crap into the language is worse than not getting good stuff in. But did they really veto here? As I read a few days ago, the guy doing the proposal just was forbidden by Google to work on it anymore. I wasn't in favor of this proposal think it's one of the better outcomes, but the form how if came to be dropped was a bit strange.
- nobleach 10y agoThis is what I'm seeing. I wasn't really a supporter of the feature... but I wasn't going to try and tear it down. Google has limited resources, so, since they didn't see any usefulness for their business model, they shot it down. They've instead chosen to throw some resources into evangelizing AMP - a technology that I hope dies quickly.