The article's flaws aside, it does give a number of specific examples of Javascript design flaws, specifically type system flaws leading to unintuitive results (like the "wat" talk).
These are real flaws, which actually occur in real code that people are writing in Javascript, and this has been the case as long as Javascript was a thing.
It is not trivial to avoid all of Javascript's design flaws, and the bugs they create, all of the time. Pretending otherwise is like pretending that "serious" C programmers always free their memory and never dereference invalid pointers. Even if you can solve certain problems by always writing your comparisons backwards, there is a design flaw there that didn't strictly need to exist. C has at least the excuse that it's intentionally very low-level.
Whether you like them or not, whether their problems end up being worse, the huge number of layers and transpilers over Javascript (like Coffeescript and jQuery) have a following because of Javascript's enduring legacy of pain. But due to the politics of browsers (and not due to Javascript's supposedly perfect design) we seem to be permanently stuck with Javascript as the only real browser language.
I agree with your points, but as far as the high level argument as to "why the web sucks" goes, they are fairly weak towards that end and not as decisive as laid out in the article.
It is not trivial to avoid all of Javascript's design flaws, and the bugs they create, all of the time. Pretending otherwise is like pretending that "serious" C programmers always free their memory and never dereference invalid pointers. Even if you can solve certain problems by always writing your comparisons backwards, there is a design flaw there that didn't strictly need to exist. C has at least the excuse that it's intentionally very low-level.
Whether you like them or not, whether their problems end up being worse, the huge number of layers and transpilers over Javascript (like Coffeescript and jQuery) have a following because of Javascript's enduring legacy of pain. But due to the politics of browsers (and not due to Javascript's supposedly perfect design) we seem to be permanently stuck with Javascript as the only real browser language.