When websites are broken in Safari it is, almost invariably, because the web developer was lazy and only ever attempted to make things work in Chrome. This has many risks, including an unintended (but still pathological) reliance on Chrome implementation quirks and undefined behaviours.

Chrome is the new IE because it is fostering the return of the lazy developer who thinks the web can be reduced to a single web browser.

Safari is not the new IE. It is highly standards compliant, it’s actively maintained, and it’s not making web developers lazy.