A lot of other very useful comments already, so this may echo some of those... Learn any language until that language isn't what you think about, as soon as you are thinking about data structures and data flow you can start to hop languages and choose another.
The second language you learn should be a pragmatic way of expressing the things you do the most, or it should be the most performant way of building what you want (either performant based on time to code a solution or on time to execute depending on what you are building...)
You could literally stop after your first paragraph.
"Learn any language until that language isn't what you think about"
That is a very good point :)
"Learn any language until that language isn't what you think about, as soon as you are thinking about data structures and data flow you can start to hop languages and choose another". This. I agree wholeheartedly. My post was to get other people stuck in the "this is how you do arithmetic operators, expressions, if loops + random videos /articles that appear saying why the language you are currently beginning to learn is dieing and why you are wasting time" hell that some people get stuck in. Like I was.
Yeah absolutely, if I came across as questioning your motivation and method then I misspoke. I applaud the principle, just wanted to point out that "reasoning out which language" has complexities...
You didn't. And yes I agree. But sometimes it's better to be broad and make a list with your basic understanding of which language is good for what that can be attached to your goals. As people are in a trade for longer and gain more understanding and they won't be as easily swayed as they when they are blind to everything.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.