-
-
-
Why not just set the default depth to Infinite and call it a day?
- 4 more replies
New conversation -
-
-
It’s not about any particular library. If shipping a new feature breaks a single website, that’s already too much breakage.
-
I see. Seems like an impossibly high bar though. I had a personal lib I used on a bunch of sites that overrode String.prototype.startsWith that broke once the official started shipping - does that mean I could have held up using that function name because of my handful of sites?
- 2 more replies
New conversation -
-
-
How widely-used does an esoteric JS library have to be to impact future native method naming, anyway?
-
All it takes is one breaking website sticking to the old version

- 1 more reply
New conversation -
-
-
Use the right names, make library owners keep up with standards!
-
That still doesn’t solve the problem unless everyone using the old version deploys the update.
- 1 more reply
New conversation -
-
-
Just let it break. If you use a library implementing known bad practices for eight years, it's time to get burned.
-
Its about the users of the sites. Not the developers.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
We might have to rename the method before shipping it in browsers.
cc