I'm a polyglot when it comes to programming languages.
I think developers are well served to learn lots of languages, because they have different perspectives, strengths, and shortcomings.
Keep in mind that programming languages are tools, and some are more suitable or less suitable for a given problem domain. Having more tools in one's toolbox is not a bad thing.
Robert "Uncle Bob" Martin is also a polygot of programming languages. He's been pretty vocal about Clojure as being the best language to learn. (I don't disagree with him, I just take "best" with a grain of salt.)
One criterion I consider for programming languages is: if I learn this language, can I get a job using it?
That doesn't stop me from learning a "dead-end" language, just tempers how much effort I put into it. I like to learn one new language every year. Sometimes it's an incremental change, like from C++14 to C++17. Othertimes it's a novel (to me) programming language like F# or Elm.
C? Definitely a skill that one can use for gainful employment. Ditto with Rust and C++.
The job-worthy programming languages are pretty well reflected in the monthly TIOBE index. C is #2 right now.
My favorite programming languages: D, Python, F#, and Elm.
The programming languages I use that pays the bills: C++14, Objective-C, Objective-C++, and C.
I don't have Clojure on my list. Yet. I plan for it to be the language I learn next year, in 2023. It's very Lisp-like. I've learned Lisp back in the 1980s. I'm aware of the blub paradox. I did not appreciate Lisp's strengths back in the 1980s, maybe I'm in a better position to appreciate Clojure's strengths today. The SICP book is available as PDF for free by the authors.
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.
I'm a polyglot when it comes to programming languages.
I think developers are well served to learn lots of languages, because they have different perspectives, strengths, and shortcomings.
Keep in mind that programming languages are tools, and some are more suitable or less suitable for a given problem domain. Having more tools in one's toolbox is not a bad thing.
Robert "Uncle Bob" Martin is also a polygot of programming languages. He's been pretty vocal about Clojure as being the best language to learn. (I don't disagree with him, I just take "best" with a grain of salt.)
One criterion I consider for programming languages is: if I learn this language, can I get a job using it?
That doesn't stop me from learning a "dead-end" language, just tempers how much effort I put into it. I like to learn one new language every year. Sometimes it's an incremental change, like from C++14 to C++17. Othertimes it's a novel (to me) programming language like F# or Elm.
C? Definitely a skill that one can use for gainful employment. Ditto with Rust and C++.
The job-worthy programming languages are pretty well reflected in the monthly TIOBE index. C is #2 right now.
My favorite programming languages: D, Python, F#, and Elm.
The programming languages I use that pays the bills: C++14, Objective-C, Objective-C++, and C.
I don't have Clojure on my list. Yet. I plan for it to be the language I learn next year, in 2023. It's very Lisp-like. I've learned Lisp back in the 1980s. I'm aware of the blub paradox. I did not appreciate Lisp's strengths back in the 1980s, maybe I'm in a better position to appreciate Clojure's strengths today. The SICP book is available as PDF for free by the authors.