(FWIW - I am not a programmer/developer)
e.g. Saying "Ruby Developer" isn't like saying "Brain Surgeon". It's more like saying "Hammer Carpenter" or "Scalpel Surgeon".
Web Developer, Embedded Developer -- these are more akin to specialization on the order of "Brain Surgeon" or "Endocrinologist". Notably, no-one's taking issue with that kind of specialization.
Maybe that part of the analogy doesn't hold up for a hospital, but it sure as hell does in a software engineering organization. If you have a bunch of people working together towards a common set of goals, it makes things a hell of a lot more complicated if everyone is just working in the language they like playing with the most, regardless of their overall technical knowledge. Organizations standardize on best practices, languages, frameworks and technologies because it simplifies things.
If you have the feeling for the music you can create music using anything. Ideas just blow to your mind. The tool, well, it's is just an interface to concretize your idea.
But I think specialization is not a bad idea.
I'm tired of an industry where it's assumed that using technical tools is the skill, rather than understanding and applying technical concepts.
I'm tired of "I'm a .NET developer" or "I'm a python developer". I want a world where we're not tied to a particular framework, where people hire expert technologists and business analysts regardless of what framework they used at their last job. Where managers truly value people and interactions over tools and process.
The inhumanity and subsequent waste of it all is really piling up, and theses posts only reinforce the ignorant and shallow perception that the tools make the professional.