IMHO it depends on the stage at which the developer is. When starting the career as a developer there's nothing wrong about being generalist. Actually, it would be ideal: learn a little bit of different languages/technologies, find what you like and your passion. Moving forward into mid-level, the developer should have a general idea of what they like, their strengths and weaknesses, and it's time to start specializing (while always keeping up with knowledge and new approaches for other technologies). A senior that is too generalist brings a lot of knowledge to the table, but it may be counterproductive because the performance will likely not be at the senior level for most of the technologies/languages... Which will the person get stuck. There's always time to grow and specialize, and they may be good for leadership/management too (if they are up to it).
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.
IMHO it depends on the stage at which the developer is. When starting the career as a developer there's nothing wrong about being generalist. Actually, it would be ideal: learn a little bit of different languages/technologies, find what you like and your passion. Moving forward into mid-level, the developer should have a general idea of what they like, their strengths and weaknesses, and it's time to start specializing (while always keeping up with knowledge and new approaches for other technologies). A senior that is too generalist brings a lot of knowledge to the table, but it may be counterproductive because the performance will likely not be at the senior level for most of the technologies/languages... Which will the person get stuck. There's always time to grow and specialize, and they may be good for leadership/management too (if they are up to it).