Bryan Cantrill explains a very interesting thought about that here: https://youtu.be/2wZ1pCpJUIM?t=1420 https://youtu.be/2wZ1pCpJUIM?t=1420 I'm sure there are

Bryan Cantrill explains a very interesting thought about that here: https://youtu.be/2wZ1pCpJUIM?t=1420 https://youtu.be/2wZ1pCpJUIM?t=1420 I'm sure there are many other factors that play into this (just look at Gary Bernhardt's "WAT" talk), but essentially, I agree that this has to be a big part of the problem. If you've been developing backend systems and asked to hold up robustness and stability guarantees for multiple years and then run into Javascript, you will likely run into situations where you have to make up for its deficiencies in that regard. That doesn't make it a bad language per se -- that's the case with any language in some aspects -- but since JS will be a new language to you, you're much less likely to accept that situation as a given.