2 ms·
Billion dollar mistake? No But anecdotally I've experienced many null-pointer runtime errors, to the point where I very strongly believe having strict or even
by armchairhacker 4y ago
Billion dollar mistake? No
But anecdotally I've experienced many null-pointer runtime errors, to the point where I very strongly believe having strict or even half-decent null checking reduces the amount of runtime errors my code produces non-negligibly. I'm sure not everyone has the same experience, but I strongly prefer languages with null safety (AKA marking a type "non-null", and then the compiler makes a good effort to ensure it's not null).
- hajile 4y agoAt 100k per year, 1B is a mere 10,000 man-years or with 4.4M devs in the US, that's less than one work day per currently-working dev across their entire career. I'm sure that I've spent weeks worth of time doing this in one form or another and I doubt that I'm alone here. By that metric, it's more like the 100B mistake.
- LarsDu88 4y agoWell said!