I'm OK with the existence of GPL software. I like it when people use a more permissive license, but your code is yours to do with what you will. What bothers me is what people say about the GPL, because I think it's misleading.
There is this common idea in the free software community that it is not hostile to commercial software. That's what I don't like. If people came out and said, "Yeah, my GPL source code has very severe restrictions that make it unsuitable for integration in commercial software," I would agree and wish them happy coding. But they don't say that. They use the misleading banner of "free," and even try to deny that it's incompatible with commercial software.
Based on all the evidence I've seen, I believe commercial software pretty much has to be offered under a proprietary license in 99% of cases. The GPL says I can't do that if I use so much as one line of GPL code written by somebody else. That means that using GPL code in my software renders it unsaleable.
So, when you said, "It is free to be used commercially … if you keep its derived works open source," I objected to that. If you can only release your software under the GPL, you're probably not going to make a lot of money selling it — it strains the definition of "commercial." You can't even use the Sleepycat model, where there's a GPL version and a commercial one.
It's your right to put your software under that license. But I think it's important for people to understand that it completely shuts out commercial use, even if the commercial use is largely original. We shouldn't downplay that.
But not because that software is being sold, or because it is profitable, or corporate, or big-business, or commercial or any of those things. It is hostile because it is "proprietary" and that (in the FSF's opinion) tilts the power balance too far towards the vendor, allowing all sorts of abuses.
Where I think you are getting confused is that some of those abuses are highly profitable and so those are the most visible successes to you.
But people like to sum this complicated area up as the GPL being "anti-business" or not "business-friendly", which is highly misleading. You'll note that quite a lot of non-software businesses are quite happy to use GPL code since a) they are not in the business of selling proprietary code and b) proprietary code gives too much power to the vendor. There's plenty of room for businesses to supply GPL software to these companies.
On that topic: Whether or not the GPL was designed to be hostile to commercial software, it is hostile to commercial software in the real world. I don't know of a single piece of GPL software that makes decent revenue on its own.
It's unfortunate if you happen to be the mythical lone inventor that all the laws that patent trolls thrive on was supposed to benefit. They were the collateral damage caused by something that was supposed to benefit society through you, and as patent laws get reformed you'll be the collateral damage caused by something intended to benefit society by curtailing them.
The other elephant in the room is web apps, which the GPL has no power over. There are plenty of people selling that software for a living while building on GPL code. If you're trying to sell desktop apps then you're now more and more competing with them. Again, the GPL has changed the environment you compete in whether you wanted it to or not, and this time it's worse competition because it's more profitable.
You really, really, really need re-evaluate your take on this. GPL is the most indie-friendly of the licenses. There's a valid gripe against it: it fractures the open source community into "people who can use GPL code" and "people who can't use GPL code". But that has nothing to do with commercialization. Once you BSD license something, it is extraordinarily difficult to commercialize the code itself.