3 ms·
I'm not in a position to remove or not remove an API - I just use it, and the only thing I'm saying there is to _consider_ backwards compatibility. If the feat
by spankalee 6y ago
I'm not in a position to remove or not remove an API - I just use it, and the only thing I'm saying there is to _consider_ backwards compatibility.
If the feature is changed, change the name so existing sites don't break. You're extrapolating far too much from that, as did Rich Harris and other persistent web component haters.
- dmitriid 6y ago> I'm not in a position to remove or not remove an API - I just use it, and the only thing I'm saying there is to _consider_ backwards compatibility. There is no backwards compatibility for a feature that was released just a few days ago and that had been behind a flag prior to the release. > If the feature is changed, change the name so existing sites don't break. You're extrapolating far too much from that There's nothing to extrapolate. These are facts. ---- Also, note: "Rich Harris and other persistent web component haters". This is the continuous incessant vitriol that spews out of Google. Coupled with Chrome playing increasingly dirty, no wonder people feel resentment towards Google and its representatives.