2 ms·
I dont see why its so odd. Looks like it was behind a feature flag. I imagine the time came where someone had to make a go/no-go call, and they decided no-go.
by bawolff 4y ago
I dont see why its so odd. Looks like it was behind a feature flag. I imagine the time came where someone had to make a go/no-go call, and they decided no-go.
It wouldnt make sense to keep it as a feature flag forever, and once it is not a feature flag it becomes much harder to backout.
- Avamander 4y ago> It wouldnt make sense to keep it as a feature flag forever, and once it is not a feature flag it becomes much harder to backout They didn't struggle with removing H2 PUSH though.
- bawolff 4y agoI mean, you're still talking about it, now, much later. If it was really no struggle people would have forgot about it at this point. H2 push is also something that degrades much more gracefully if missing compared to an image codec. Nonetheless, people haved removed image codecs before (rip XBM). Harder is not the same as impossible.
- Avamander 4y agoTrue, because I saw how it was just being added to software/frameworks. Some parts of the web move slower than Google expects, I have a feeling.