Comment by nobleach

If anyone is building using experimental features that are either flagged or unflagged in Chrome, that's NOT on Chrome. For example, if I built a feature based on Chrome's weird Observables, sure, I could do it... it would work nowhere else. If you're actually seeing this happen, who do you blame in this situation?

IE flat out refused to implement features that were agreed upon by standards bodies. They pushed for VML development and ignored SVG. They ignored CSS3 in favor of their DirectX filters. Chrome does indeed put experimental features out there AFTER they support the standards. Firefox also has agreed to a set of web standards and is simply behind on implementation.

Having lived(as a developer) through IE4 - IE9, I reserve that title of "the new IE" for the worst offenders.