Having access to a representative spread of devices is the reality of web development. As a web developer that doesn't own any Android devices, I was "forced" to buy a couple of Android devices so that I could squash bugs (some of which couldn't be replicated in emulators) and to refine aspects of the physical touch experience that emulators cannot emulate. I don't resent these purchases, because I understand it's the reality of developing for a diverse open web.

And yet, oh how often I hear developers resent having to buy an Apple device. Every time, I look at my little stack of Android devices and instinctively roll my eyes.

> Cheapest option is detect if they're a Safari user and tell them to use another browser

I suppose the cheapest option for me was to detect if they're an Android user and tell them to use another device. It sounds silly to say it — it is silly to say it — but that's exactly the same logic.

If you're developing for the web and you're not testing you're site on real hardware, including a handful of iPhones and a handful of Android devices, your not actually testing your software.

You can't just check Chrome and assume everything else will exhibit the same behaviors. Standards exists, but so do bugs.

quote: "GitHub-hosted runners are available with Ubuntu Linux, Windows, or macOS operating systems." source: https://docs.github.com/en/actions/concepts/runners/github-h...

> A lot of folks want to run tests off a GitHub action I.e. on a server somewhere.

Understandable, but also if you're dealing with these sort of projects, you kind of have to setup that sort of automation yourself in an office/someone's house, unless you find some provider that already hosts that sort of thing, like the various Apple/vendor-specific services for that.

It's also not a very new thing really, MacStadium for example been around since like 2010 sometime.

GitHub has been providing macOS runners for a while now.