4 ms·
Deprecating == is probably a good step. Or better yet just turning == into === and removing that. That would cause some chaos thats for sure...
by cozuya 11y ago
Deprecating == is probably a good step. Or better yet just turning == into === and removing that. That would cause some chaos thats for sure...
- UnoriginalGuy 11y agoThey don't have to remove anything, just repeat what they did with "use strict" but make it, uhh, even stricter. Just a subset of JS which is only the good parts. Actually "use strict" actually makes JS an almost good language as mistakes are immediately flagged rather than "working anyway." But strict mode doesn't go nearly far enough in my opinion. I will say for backwards compatibility you're always going to have to write "===" the only thing a flag would do is break "==" on purpose.
- sjrd 11y agoIt seems "use strong" is for you. https://developers.google.com/v8/experiments https://developers.google.com/v8/experiments