There's no room for rock stars in my tightly organized classical and jazz ensemble.
I let go of 2 rock star developers in May. Their stars were so bright they did not seem to understand what they were actually being asked to do. I helped them on their way to finding challenges suitable for their skills and have been cleaning up after them ever since.
I completely respect people who take the art of application development seriously and do want to attract that kind of talent. What rock star implies to me is something more than a soloist, it's someone with an almost pathological urge to show off his or her talents by solving challenges. A challenge could be a bug, or an infrastructure issue, or something else, but they have to address it the moment they notice it. Feeding this urge is not quite the same thing as participating in a structured process for delivering solutions to technology challenges.
I have had guys with such talent they could build web applications sophisticated enough to be unrecognizable as web sites and completely unusable in terms of core functions. The code does something interesting in the background, but I really don't care because the project is suddenly 300% over budget and there's no end in site. Their project managers don't always know what's going on because these developers don't actually tell anyone what they are going to do - they do what they feel like and you get to live with it.
Case in point: the 'KC Box'. This name comes from a rock star developer some might think at the level of a Van Halen, with the way he promotes his personal brand. He was the lead developer on a website built for a client using an open source content management system. 9 months into the project, 100% whitescreens, user logins had been shut off, you could not enter new content, etc. Literally nothing worked, but he did get some interesting contributions to a css preprocessor out of it.
This is the kind of thing I eventually end up with from rock star developers. It's not like they are building things that are sustainable or that other people can contribute to, they are building things to satisfy some internal need.
What's more valuable to me is people who can learn to see the goals of the group of people they work with, contribute to it, communicate about the areas where they see issues and put processes in place for how to address them. I don't have some meaningless label for them, I just get better results with structured development processes and people who know how to work in teams.