17 replies

1. Alan Dávalos Bluesky 8 min later

   Not quite a calendar but I usually use webstatus.dev for that purpose

2. Zach Leatherman Bluesky 24 min later

   A ha, here’s the thing: webstatus.dev?q=baseline_s...

   Thanks @alangdm.bsky.social!

   1. Alex Russell Bluesky 26 min later

      We should all be super sceptical of the "widely available" thing. Users shouldn't be on 30 month old browsers, ever. The Cheome team should know better than to create an attractive nuisance like this.

      1. Zach Leatherman Bluesky 29 min later

         My hunch was that 30 months was too short to match reality 🫣😅

         1. Alex Russell Bluesky 34 min later

            It's not. We keep doing audits for Office to see enterprise use, and it's generally a security problem for any enterprise of they have users on engines that old. We're doing them a favour by being more aggressive in most cases.

            1. Alex Russell Bluesky 35 min later

               *if

               *sigh*

            2. Mastro.{js,ts} Bluesky 1 hr later

               yeah, but nowadays the long pole are private iPads that don’t get iOS/Safari updates anymore.

               1. hckr.studio Bluesky 3 hr later

                  and Chrome on older macOS as well.

                  1. hckr.studio Bluesky 3 hr later

                     On older Macs you can do almost nothing, because the AppStore is broken and the web is broken as well. Too aggressive everything.

      2. Alex Russell Bluesky 32 min later

         The idea that we'd create a disincentive to use a feature for almost *3 years* after 90+% uptake is 🤦🤦🤦

         I get the ESR thing, but this isn't a responsible way for us to be advising web developers about their options. The name alone is a real problem.

         1. Zach Leatherman Bluesky 35 min later

            Ah, yeah. I get that. I would welcome a Baseline that was PE-aware and usage driven too

      3. Sérgio Gomes Bluesky 34 min later

         There are a few use-cases. E.g., when collecting RUM data we want the script to work mostly everywhere, not crash on unsupported syntax, so we know the # of users left on older browsers. We've been (carefully, to avoid bloat) transpiling to ES5 for this, but "widely available" might be a good fit.

      4. Duffeh Bluesky 37 min later

         Features aren't all equal as well, like fetch priority could be used as soon as chrome supported it, and without waiting for widely available etc.

3. Zach Leatherman Mastodon 25 min later

   Here are the Web Platform features sorted by upcoming Widely Available status: https://webstatus.dev/?q=baseline_status%3Anewly&columns=name%2Cbaseline_status&column_options=baseline_status_high_date&sort=baseline_status_asc&num=100

   HT https://bsky.app/profile/alangdm.bsky.social/post/3mjkakj4ofc25

4. Curtis Wilcox Mastodon 10 hr later

   @zachleat
   I just found this chronological list grouped by month. There's even an .ics link.

   I'm on my phone so I haven't looked more closely.

   https://rviscomi.github.io/timebase/

   1. Curtis Wilcox Mastodon 1 day later

      @zachleat
      The repo's README reveals more features, like a view of only the Widely Available items and a BCD key view.

      https://github.com/rviscomi/timebase

      https://rviscomi.github.io/timebase/?status=widely-available

      https://rviscomi.github.io/timebase/bcd/?status=widely-available

      1. Zach Leatherman Mastodon 1 day later

         @cwilcox808 that is great! I did find this view too: https://fediverse.zachleat.com/@zachleat/116409569423639060