> Those features aren’t bad, just not my favorite. “Bad” usually comes in the form of unilaterally shipped features that take a long time to fix, retroactively

> Those features aren’t bad, just not my favorite. “Bad” usually comes in the form of unilaterally shipped features that take a long time to fix, retroactively standardize, or undo (e.g. vendor prefixes, <dialog>, window.event, etc). Again, once shipped, they’re shipped. They linger around in the platform, working in some browsers, never in another, frustrating developers. It produces brittleness. This is a problem created by browser diversity, not one that browser diversity would solve.