It's strange too, because if you are building a production-ready (i.e., not a proof-of-concept demo using bleeding edge technologies supported in only one browser) website or webapplication, the bare minimum level of browser support that grants you a very modern set of features you can depend on is to only support up-to-date evergreen browsers. That means Chrome/Chromium, Edge, and Firefox.

I can get dropping Edge if you are an individual developer and simply don't have any Windows machines around (testing websites from a VM really sucks), but going Chrome-only pushes us back to the monopoly position that harmed our field so much in the first place.

Actively moving towards a webkit-monoculture ultimately harms our profession.