I used to apply for JS jobs, and the interview would have questions like "What do you dislike about JS?" I couldn't find much to dislike and never got those jobs. Maybe it's a sign of proficiency when you're good enough at a language to hit its limits.
I'd say the other effect is when you join projects built by experienced but non-senior people, it tends to be overengineered. Overengineering shows the ugly side of a language. Everyone assumes that this is normal behaviour for the language, when it's frequently not.
and unlike these other languages there s not usually one or two ways of doing things. there's so many different frameworks, build tools, countless stacks beyond measure. when someone is force converted onto node they're more likely than not to have poor footing, be unable to make the typical sloe steady grind into proficiency they would with a less diverse language like python or ruby.
- the sense that I never really can be sure where the code is executing at a glace;
- the (compared to Python) cruft-laden syntax
JSON was a win. I nearly forgive JavaScript for begetting JSON.
And in a negative way as well :-) Ask me how I feel about php.
This is, though, a very excellent point.
Negative views about PHP is completely justified :)
You wouldn't make this statement if to compare bogosort and quicksort, would you?
JavaScript sucks. It isn't the best choice for any problem except where you are forced to use it (the web browser). The only reason we still have it is inertia. PHP is in the same camp.
Programming languages have evolved. We know how to do better now.