I mean the GPL actually defends your right to do whatever you want with the software including selling or renting it out.
What it restrict is what limitations you can put on those who use it, but (and here comes the nitpick): prohibiting others from using something in a certain way isn't what I'd call "commercial use" or "use". I guess a lawyer could argue that but in everyday speak, no.
> I mean the GPL actually defends your right to do whatever you want with the software including selling or renting it out.
But realistically, practically, you can't. There is nothing to sell if the software has to be open source. The list of commercial GPL applications is really short compared to the millions of applications which include BSD-licensed code.
This is not true. Many small but successful companies are released their code using AGPL3 license, so you can see and contribute to the code, but cannot compete with them using the same code.
The typical business model is a paid hosting and paid support for the product.
> so you can see and contribute to the code, but cannot compete with them using the same code.
You actually can.
You just cannot without giving back.
That's the intended beauty of it.
Edit: let me point out that I am not an AGPL evangelist. I'm less annoyed at it than I used to be but I still prefer liberal licenses for almost everything.
This is wrong. 3-clause BSD requires reproduction of copyright notice. You cannot distribute commercial derivatives of BSD-licensed code without including attribution. It’s literally clause two.
That’s why I’ve asked about the modern BSD license, the one without the advertising clause.
But even with the old one, having to add one more disclaimer to the usual page of disclaimers somewhere in the documentation is not a problem, while meeting requirements of copyleft licenses - even non-viral ones - can be problematic.
The GPL prohibits some commercial use.
The BSD license does not.