> I don't want to be unreasonable, but Google used to at least generally support the idea of the open web.
This is a Machine Learning product, I don't think anyone at Google, at least as part of this team, is trying to "get you" or destroy the open web or something. This isn't even a case of Google using something non-standard -- WebComponents is part of the standard, you can even see it in Mozilla's MDN [0]. Firefox, Safari, Edge, et al simply haven't implemented it yet (or landed in stable). Is that somehow also Chrome's fault?
Filing a bug report is good, but ranting on HN about how this is a sign of Google trying to steal the open Internet is at best unnecessary, and absolutely unreasonable.
Coincidently, I'm working on an application that uses complicated SVG with CSS animations, and I've spent a ton of time optimizing it. I've never tested it outside of Chrome before today. To my surprise, while everything works fast in Chrome, in Safari it's bearable, but in FF it's simply too laggy to use. Now, I probably won't ever get to fix the performance issues in FF and Safari, simply because I don't have the time. Am I also out there trying to destroy the open web? Maybe I'm just bad, not evil.
I mean, embedding data into html looks bad, but is it really worse than loading a script separately? This is basically the "bundling" on the HTML layer, i.e., what HTTP/2 should offer.
For a website like Airbnb, 1.9M for total asset size doesn't seem bad...
Um, pretty sure QUIC was in the pipeline a few years longer than AMP. Besides, it's literally a protocol in the network stack -- would you say IPv6 is an enemy of the web and underlying internet?
Proof by analogy is fraud. You should know better.
If you really want to go down this path -- a broken clock is correct twice, as two discrete points in a continuous time space. The act of looking at the clock is analogous to sampling one discrete point in the time space. The possibility of sampling those two points at any given time is zero.
So no, a broken clock is not correct twice a day. Also, please stop proving anything with analogy.
Please, for the last time, stop using this rhetoric. How would you like to be called an idiot? As a developer and a user, I'm deeply offended by this condescending attitude.
I really don't know what people like -- apparently opt-out is bad, so now we're using opt-in. Still, "opt-in" is bad because it's becoming a toilet? How do you expect _any_ platform to work? Self-host everything?
I'm not a citizen. I come here legally. I pay my taxes. I pay for my insurance. This is not the minority case by the way, all your H1b colleagues as well as F1/J1 students are like this. Should we still die because we're not American citizens?
>Although I would prefer to concentrate on the 10s of millions of non-citizens and illegal aliens who receive tax payer funded health care.
I feel like I should remind you here that many non-citizens are actually tax-payers. Taxes are paid in many different ways, but let's forget about that here for a second and realize that many non-citizens actually come here legally to work.
A blanket statement like that really doesn't mean anything. Same arguments were given about dreamers using tax-payer money, without realizing many of them actually are tax-payers as well.