| 00:51 | <foolip> | smaug____: synx XHR actually already has a deprecation message, but not with a date or anything to suggest when/if it'll be removed |
| 00:52 | <smaug____> | oh, great |
| 00:52 | <smaug____> | foolip: Mutation Events too ? |
| 00:53 | <foolip> | which I consider a bug. if it seemed plausible that it'd get the job done, I'd support giving it 1 year until removal, but I think the usage there is much too spread out in different kinds of libraries and other hard-to-update places |
| 00:53 | <foolip> | smaug____: I haven't personally looked very closely at the prospects for Mutation Events, but someone (tm) really should come up with a plan for that :) |
| 00:54 | <foolip> | but not me, not today, it's Saturday morning and Tokyo requires my attention :) |
| 00:54 | <smaug____> | I don't think we can get rid of horrible APIs in the platform if browsers don't warn about their usage |
| 00:54 | <smaug____> | it is Saturday indeed |
| 00:56 | <foolip> | smaug____: smaug____ in https://github.com/whatwg/xhr/issues/20 I said a lot of what I think about deprecations to drive removals |
| 00:57 | <foolip> | short story is I'm skeptical that it's enough, there are other ways to drive down the usage that are more active, but we haven't actually tried the 1-year thing, so it's possible it's not as hopeless as I think |
| 01:02 | <smaug____> | hmm, what has happened to mutation events usage. Gecko telemetry says it is very low |
| 01:04 | <smaug____> | sync XHR is down too |
| 01:05 | <smaug____> | https://www.chromestatus.com/metrics/feature/timeline/popularity/465 is quite promising, I'd say |
| 01:06 | <Domenic> | One has to wonder if that's just the internet getting bigger :P |
| 01:07 | <Domenic> | but yeah, foolip and I often debate this, I like pretending it will linearly extrapolate to zero, whereas he's more realistic and thinks it's likely leveling off |
| 01:08 | <foolip> | good point, a constant number of affected users would still look like a 1/x graph or similar |
| 01:09 | <smaug____> | big sites like Google was using sync XHR and then at some point dropped it, I think around the time certain browsers started to warn about its use |
| 21:39 | <tobie> | annevk: fixed the html diffs issue in pr-preview. LMK if you spot anything weird. |