Chrome is doing the "I make my own web standards and push them through, ups now my feature is standard incompatible so I try to force change the upcoming standard just before it gets committed" thing IE had done in the past (it's e.g. the main reason why you sometimes end up with CORS issues on FF, the site isn't standard compatible as it doesn't handle a certain thing the standard requires from websites but due to a last minute exception for chrome doesn't require browsers to enforce).
And Safari does the "I don't adopt new standards forever and have strange bugs" IE think. Funnily like IE there are a lot of devs which swear that it has no strange bug problem (because they mainly use libraries developed on/for or at least tested with safari, but if you use some more newer tech it Safari support can be quite costly).
Yes both Chrome and Safari are "the new IE" but for different reasons
I think people make too much of Safari lagging in the adoption of standards. Yes, they lag behind on what Chrome is pushing but they're also ahead on other features, like color spaces.
I'm familiar with Safari strange bugs but it's usually while I'm testing with VoiceOver so I have fewer occasions to notice bugs with Chrome or Firefox, which don't work as well with VoiceOver overall.
I think of Safari being the new IE because it's not as evergreen as other browsers; old but still usable iPhones and iPads can't run the current version and aren't allowed to run anything else. Thus, developers have more reason to care about what a browser from 2+ years ago supports.
To be fair, IE and Netscape existed before there was an active standards body. 25 years ago standards were developed in a waterfall like process that took years.
The only time new features were released was when IE or Netscape pushed them.
