I'm not terribly familiar with the landscape, but my suggestion is broadly applicable: learn both.
A developer shouldn't be constrained to a single language. Pick the one that's suitable for the project you want to work on. For the next project, do the same. In my experience you'll find it progressively easier to pick up new languages (and stacks, and paradigms, etc.) each time you do it.
IMO, a developer's goal should be to understand and implement design patterns, not individual languages.
... and for the record, I say this as someone who prefers a single language (Python) to all others I've encountered.
I'm not terribly familiar with the landscape, but my suggestion is broadly applicable: learn both.
A developer shouldn't be constrained to a single language. Pick the one that's suitable for the project you want to work on. For the next project, do the same. In my experience you'll find it progressively easier to pick up new languages (and stacks, and paradigms, etc.) each time you do it.
IMO, a developer's goal should be to understand and implement design patterns, not individual languages.
... and for the record, I say this as someone who prefers a single language (Python) to all others I've encountered.