I'm somewhat intrigued by the source of this sort of question, and about
beliefs along the lines of "which language should I learn (first)?"
I'm sure there are lots of potential pitfalls to picking any computer
language to learn first, perhaps some more than others. But the first
computer language isn't really about learning that language so much as it
is about learning how to program: how to approach problems, how to break
things down, how to build things up, how to make sure what you've written
works, how to make sure you are solving the right problem, etc.
I can't really imagine any one language would actually be a bad choice to
start with, as long as one has support, and there is adequate
documentation. The great difficulty lies, I feel, in these other aspects of
programming.
One thing I see here and on other forums is the concern about picking the
one right language. This is a pink unicorn. There are so many languages,
and so many problem spaces, so many things that one can and probably should
learn, that what becomes even more important is learning how to learn new
languages, new libraries, new frameworks, new approaches, honing skills in
design and architecture, testing, deployment, and all the rest.
What actually concerns me most that seems inherent in the question is a
state of analysis paralysis -- just pick up one and go. Once you learn one,
it's easier to learn another, and another, and so on.