Mostly agree, except for the first point. There are bad languages. Java is a bad language, javascript is a bad language, php has been and to some extent still is a bad language. The point is that we some times have to use bad languages and a language being bad doesn't mean one shouldn't learn it. In fact, I'd say learning bad languages is a good thing, because then you learn why they are bad.
Go program in Java for a few months and learn why rampant boilerplate code, rejection of operator overloading, and overuse of wrapping classes make for a bad language. Go program in javascript for a few months and learn why the need for === is a sign of a bad language. Go program in php for a few months and learn why lack of consistent naming conventions, over proliferation of similar yet different solutions to problems, and general lack of language design direction makes a bad language.
I understand your point, new coders shouldn't avoid learning important and popular languages just because they are bad, but we also shouldn't blow smoke up people's behinds and pretend that all languages are good when that simply isn't the case.
When I say, there are no bad languages, I do not mean it in a technical or syntactical way. Nor am I advising anyone to commit themselves to learning PHP, JavaScript or Java even when they don't want to. The only thing that I want to convey from my first point is that no language is without its pros and cons. If we dig deep enough, every single tool out there will have its own disadvantages but that does not mean that we should stop using them out of minor inconvenience. We just need to align our goals and what we want to achieve and then choose the tool accordingly.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Mostly agree, except for the first point. There are bad languages. Java is a bad language, javascript is a bad language, php has been and to some extent still is a bad language. The point is that we some times have to use bad languages and a language being bad doesn't mean one shouldn't learn it. In fact, I'd say learning bad languages is a good thing, because then you learn why they are bad.
Go program in Java for a few months and learn why rampant boilerplate code, rejection of operator overloading, and overuse of wrapping classes make for a bad language. Go program in javascript for a few months and learn why the need for
===is a sign of a bad language. Go program in php for a few months and learn why lack of consistent naming conventions, over proliferation of similar yet different solutions to problems, and general lack of language design direction makes a bad language.I understand your point, new coders shouldn't avoid learning important and popular languages just because they are bad, but we also shouldn't blow smoke up people's behinds and pretend that all languages are good when that simply isn't the case.
When I say, there are no bad languages, I do not mean it in a technical or syntactical way. Nor am I advising anyone to commit themselves to learning PHP, JavaScript or Java even when they don't want to. The only thing that I want to convey from my first point is that no language is without its pros and cons. If we dig deep enough, every single tool out there will have its own disadvantages but that does not mean that we should stop using them out of minor inconvenience. We just need to align our goals and what we want to achieve and then choose the tool accordingly.