The problem of the GPL is that it assumes that infinite forking of software is a good thing (more choice!) when the opposite is normally true - it's better to have ONE project that isn't perfect for anyone, but that is easy to find and actively maintained, than it is to have a large number of forks each with the pet feature of different users.
For library code it's a different story. If I write a library I'd hope to get commercial use of it. I suppose you could argue that in that case you should be using the LGPL rather than BSD/MIT/CDDL/Apache, but I honesly think the LGPL is underused simply because of it sounds a bit like GPL and it makes people nervous.