I don't blame rain when bad drivers get in car accident. It really is true that there are bad drivers in the world and that they are numerous.
That is faulty reasoning for a couple of reasons. What size is your sample pool out of total developers? Degree of passion in an opinion is not evidence of it being widespread or how widely spread.
Although a faulty premise the point you make is still valid, but more complex than you are suggesting.
* Perhaps many developers are not properly prepared or educated to that language or in general. Is that language a common language of primary focus in many computer science programs? There isn't any established licensing or certification program to qualify competence in the industry for any language.
* Perhaps there is a common lack of motivation to perform well in this language. Many large organizations set performance targets that are far out of alignment with product quality or code authorship.
* Perhaps there is a common lack of mentoring. It could be reasoned that sometimes new developers are thrown to the wolves at work and the people they are supposed to be reliant upon for guidance are just as insecure.
An example I work on a team at a really ginormous company that is incredibly insecure. I spend most of my time performing copy/paste instead of writing code and the code has all kinds of problems. It would be faulty to blame the language for such poor implementation and such poor internal development.
By far the most common behavior I have observed in the big established corporate world is that most developers enter software development careers from a computer science education. Most of the time the languages of primary focus in education are C++ or Java but not JavaScript. The result then is to make JavaScript behave like something an inexperienced developer is more comfortable with using an architecture in a box and when that doesn't fully work simply add tools until it does work. The fact that JavaScript is multi-paradigm and can behave like Java, somewhat, isn't helpful.
These same frustrations exist for a variety of other popular languages as well. The only one thing that separates JavaScript from other popular languages, in this regard, is that JavaScript is the language of the web. If you are forced to work on that software platform JavaScript is forced upon you to all your emotional anguish and sad loathing.
That is faulty reasoning for a couple of reasons. What size is your sample pool out of total developers? Degree of passion in an opinion is not evidence of it being widespread or how widely spread.
Although a faulty premise the point you make is still valid, but more complex than you are suggesting.
* Perhaps many developers are not properly prepared or educated to that language or in general. Is that language a common language of primary focus in many computer science programs? There isn't any established licensing or certification program to qualify competence in the industry for any language.
* Perhaps there is a common lack of motivation to perform well in this language. Many large organizations set performance targets that are far out of alignment with product quality or code authorship.
* Perhaps there is a common lack of mentoring. It could be reasoned that sometimes new developers are thrown to the wolves at work and the people they are supposed to be reliant upon for guidance are just as insecure.
An example I work on a team at a really ginormous company that is incredibly insecure. I spend most of my time performing copy/paste instead of writing code and the code has all kinds of problems. It would be faulty to blame the language for such poor implementation and such poor internal development.
By far the most common behavior I have observed in the big established corporate world is that most developers enter software development careers from a computer science education. Most of the time the languages of primary focus in education are C++ or Java but not JavaScript. The result then is to make JavaScript behave like something an inexperienced developer is more comfortable with using an architecture in a box and when that doesn't fully work simply add tools until it does work. The fact that JavaScript is multi-paradigm and can behave like Java, somewhat, isn't helpful.
These same frustrations exist for a variety of other popular languages as well. The only one thing that separates JavaScript from other popular languages, in this regard, is that JavaScript is the language of the web. If you are forced to work on that software platform JavaScript is forced upon you to all your emotional anguish and sad loathing.