This is like being in the 2000s and saying "Why would I use anything but IE5, everything works with it"

The market share is what makes those circumstances exceptionally rare. Meanwhile we're having to use safari specific fixes and refrain from using he newest standards just because of safari

▲

dep_b 11 hours ago | parent | next [-]

It’s much easier to make stuff work with Safari first then last.

▲

troupo 11 hours ago | parent | prev [-]

Where "newest standars" are inevitably "Chrome-only non-standards".

Safari is not just fine. It's more than fine: https://wpt.fyi/interop-2025?stable

	▲	realusername 6 hours ago \| parent [-]
		Safari's problem has never been the lack of supported standards, more that the support is buggy. You'll find that yes the feature is there but it throws a nonsense exception in a weird case and same in CSS. It's also the last non-evergreen browser so bugs take longer to fix than Firefox or Chrome, compounding the problem.