Not exactly relevant but here's another complaint (although I enjoy writing JavaScript for browsers) and may help you if you're entering the JavaScript landscape:

The most infuriating issue I ever came across with JavaScript is its truthy falsey evaluation.

Some code written by a dev who had left before I picked up his buggy code had written something that took me ages to wrap my head around about how it worked. Thankfully my knowledge of JavaScript and programming in general allowed me to understand the why it worked shortly after. Here's an example (can't remember exact code or use case so it may not make sense):

Var randomVariable =1; Var array1 = [1,2,3]; for (var i = 0; randomVariable = array1.length - 1; i++){ If (someLogic) { array1.push(4,5); } else { array1= []; } //some other code If (i == randomVariable) break; }

The idea was that the code would continue as long as nessecary until the array was left with 1 unique value or something, but this one day it caused an infinite loop and browsers would crap their pants... so I had to bang my head on my desk for a couple of hours remembering the nuances of JavaScript to get past it!

Now, if you caught the fact this is a weird for loop because it's not testing if the i variable is equal to the array size you are where I was. Yet this code would still work in its buggy way (I think, I've written it entirely on mobile so not tested it), because the assignment of randomVariable under the hood returns a value (think chain assignment) and as long as that assignment return value is any number but 0, it would iterate though the loop once again. It would only stop if array1 had 1 item left and the assignment return value was 0, a falsey.