You can't even test on Safari without investing in Apple specific hardware. It's not cross platform and Apple doesn't help devs either. Even MS provider VMs so you could actually test their damn closed browser.

Even the open source Epiphany Web browser from GNOME can roll out updates to the core WebKit faster than Safari. It's not a 1:1 comparison, but it's the best way I can test WebKit from Linux even if Safari lags on releasing.

Until you've actually developed for mobile Safari, and had to deal with absurd bugs and anti-user problems that have been around for a decade, it's difficult to understand the scale of the problem.

Even if you ignore any of the new shiny APIs and features being ignored by Apple, the general state of web support by Safari is atrocious and forces developers into many one-offs specially for that browser. This is actively anti user.

There are a lot of bugs that only show up on Safari, and there's no way to test them without a Mac or a service like BrowserStack.

Supporting Safari takes up a huge amount of my time as a developer. That's why you see these articles.

And nobody cares much outside chrome-web developers, that’s why you only see these articles from them and not users.