I think that's sort of the point being made -- you might not find eclipse programmer, but you'll find plenty of Java or .NET programmers, and those are tools also.
I think you're missing the original point I was trying to make. Java and .Net aren't really the tools, they're the medium in which you work. Just like that civil engineer understands the trade offs invovled with different kins of concrete ad using it in different ways, the Java programmer understands the trade offs involved with the API and VM, in addition to generic CS tradeoffs. Look at the following two fake resume excerpts:
Bob T. Builder :
Civil Engineer with Emphasis in Concrete Stress
---Skills---
Autocad :
Industry Used Physics Modeling Software
Suzie M. Hacker :
Java Programmer
---Skills---
Eclipse :
Ant
Learning to really use Eclipse or Visual Studio well takes a surprising amount of time. So, IMO it's reasonable padding for a resume, but people don't call themselves Visual Studio developers.
What people most often identify with seems to be the frameworks they are using. So you will see someone call themselves a .Net Developer not C# .Net coder even if that's what they do. They don't know all of .Net but they feel confident they know how to approach most .Net issues and they happen to use .Net and Visual Studio.
I could have looked at the Spring stack or Coca, but I think the point still stands. Even if someone is calling themselves an OX X developer they are talking about knowing the same type of thing as a .Net developer.
