[jsgo]

Memory is hazy, but from what I've read most people that call Chrome the new IE is because it likes to incorporate non-standard aspects that other browsers don't (because they're not standard) which causes apps to lose functionality (or outright break) outside of Chrome.

I can kind of see it both ways. I appreciate that Chromium browsers may have little extras you can tap into as it'll make for neat features (Project Stream and I imagine later Stadia is because of that sort of thing), but it does break browser compatibility so it runs the risk of replicating that "works in IE" experience from way back when.

The IE I don't specifically miss though was needing to support older releases of it at work, personally. But I could see disliking the "what do you mean it doesn't work in Safari/Firefox/etc.?" discussions that may happen.

[zinekeller]

I do also appreciate the so-called experiments by the Chrome team, but my gripe is that they are implemented directly instead of hiding it in flags. Other people do want to comment on the specific implementation and probably change the API so that for example it is less destructive when there are new subfeatures in the specification. I personally hate how they handled the Polymer specification: thry are still using their draft instead of the standardized version in YouTube for example.

[sofixa]

> I do also appreciate the so-called experiments by the Chrome team, but my gripe is that they are implemented directly instead of hiding it in flags

IIRC all of them start as flags, and there are tons of them available, most disabled by default. Most move up to stable and enabled by default after some time and testing and feedback though.