4 ms·
How about JavaScript and '==' versus '==='? Or going back and forth between languages that use '==' and JavaScript? Let's say over all of history there have b
by com2kid 7y ago
How about JavaScript and '==' versus '==='?
Or going back and forth between languages that use '==' and JavaScript?
Let's say over all of history there have been a million C/C++ programmers, and each of them has made that mistake ~5 times, in total.
And let's be generous and say that 95% of the time it was found before it got anywhere near production.
That is still 250,000 bugs introduced.
Not to mention how much time is spent tracking down the bug once it has been in the code base for awhile. If it goes unnoticed for a couple of weeks debugging becomes non-linearly harder.
- gridlockd 7y ago> How about JavaScript and '==' versus '==='? > Or going back and forth between languages that use '==' and JavaScript? That's a mistake I make often, but it's exactly because Javascript is different here from all other languages that I use. Let's say I had to use a language with ':=' as assignment, I would still accidently type '=' all the time. > Let's say over all of history there have been a million C/C++ programmers, and each of them has made that mistake ~5 times, in total. > And let's be generous and say that 95% of the time it was found before it got anywhere near production. > That is still 250,000 bugs introduced. Well, so what? That's 250,000 out of maybe a hundred million bugs. I'm not saying it's good language design to have this behavior, quite the opposite. I'm saying it's not a big deal, especially considering all the other footguns in these languages. It's also not like these languages are going change it.