I like BrowserStack, and I use it a lot at work, but it's way too slow to be part of the core code, test, debug loop, simply because it's far from a native experience.

As long as that's the case, support for Edge/IE is always going to be a second-class citizen for me. Safari, too, since that's only on Mac OS, and God help you if you need to debug web apps for iPads. There is no good way, and the only tool you have is a shotgun (dev tools don't always work with BrowserStack & mobile Safari, and we currently have an iPad, but no Mac to debug it with.)

> God help you if you need to debug web apps for iPads

Why invoke God, a Mac is a few hundred $s?

Honestly I think second class citizen is acceptable, even preferable. Chrome is always available if the site is just too compelling to ignore. But most of the web is user-hostile, and directs its barrels at Chrome.

"Just shy of 1000" is a curious definition of "a few hundred". And definitely not a trivial expense for many OSS/indie developers.