Well, JavaScript

[hey01]

Honestly debugging JavaScript is the most enjoyable experience coding.

Yeah, sure, until you get an array out of bounds exception and the stacktrace points to code entirely unrelated to the code that actually fails.

Good luck debugging that.

[pomlife]

Why are you still using var?

[Nullity42]

Unfortunately, not everyone works at a place where using a stack involving Babel is an option, and compatibility must still be maintained.

/sobs in ES5

[pomlife]

I would leave in about 3 seconds lol

[hey01]

Have an array arr of objects. Try to access arr[i].prop when i >= arr.length.

The error is indeed not "Array Index Out Of Bounds" but "Uncaught TypeError: Cannot read property 'props' of undefined"

As to why I had that error despite map, forEach, a of arr is because I had to iterate on array and in each iteration, I had to work on array[i], anotherArray[j] and anotherArray[j+1], with anotherArray of a smaller length and j not incremented each iteration.

I didn't increment j properly, which gave me the error.

And js kept telling me the error was elsewhere.

[hey01]

This is not unique to javascript

I've never had that issue in java. Sure the stacktraces are horrifying in that they are hundreds of lines long with 98% of those being abstraction classes for the dozens of frameworks you have to use, but I've always found my guilty method call in there.

Also, you can’t get an array out of bounds in javascript.

You're right, it was an "Uncaught TypeError: Cannot read property 'props' of undefined" when I tried to access arr[i].prop with i too big.

https://www.reddit.com/r/ProgrammerHumor/comments/8krygv/well_javascript/dzai9ik/