> because things like Safari ...work really well

Are we living in the same universe? We manage a fleet of tablets (both Apple and Android) for a healthcare company whose EMR is web-based. And because of that Sarafi has made our lives miserable. So much so that we're migrating to Chromebooks.

I've been developing for the web for 15 years. The first half was spent battling Internet Explorer. Now it's Safari.

▲

shuckles 25 minutes ago | parent | next [-]

The people complaining about Safari often are running enterprise crapware that requires some esoteric Chrome API or bug to operate correctly and should actually be an app on iOS but cannot be funded as such because its creators don’t care about its users.

	▲	jorvi a minute ago \| parent \| next [-]
		Well, formerly you would have been right, but WebUSB and whatnot are gaining a lot more traction. I didn't take WebUSB seriously until I steered someone to flashing a small firmware onto something and they could do it straight from the browser! And it was a nice workflow too, just a few button and a permission click. Two other examples I can think of are flashing Via (keyboard) firmware and Poweramp using WebADB via WebUSB to make gaining certain permissions very easy for the layman. I imagine it's gonna get more and more user in enterprise too. Firefox is seriously behind by refusing to implement it.
	▲	mexicocitinluez 4 minutes ago \| parent \| prev [-]
		> some esoteric Chrome API or bug Or simple things like supporting 100vh consistently. Is that estoric?

▲

acdha an hour ago | parent | prev | next [-]

There are some proprietary Chrome APIs but if you’re not using those it’s been pretty rare to have major problems in recent years. I open a couple of bug reports a year against Chrome, Firefox, and Safari—mostly accessibility related—but most of the time it’s been a problem with code written specifically against Chrome rather than code which couldn’t work in the other browsers.

▲

clickety_clack an hour ago | parent | prev [-]

I’m a developer too, but the developer experience doesn’t matter to users. As a user of the app, it’s fast enough, cleanly designed, seems to be reasonably private and secure, and I haven’t hit any website with it where I’ve had to download chrome to view it or something.

	▲	mexicocitinluez 10 minutes ago \| parent [-]
		You're a developer but you can't connect the dots between "features being hard to build and the inconsistencies between other browsers vs Safari" to how that might effect the user?