I think you misunderstood. My software is not permissive. My software is closed source, but based on a big open source project with a permissive license. It's a tool that helps users of the big open source solution.
I can sell licenses to my tool because it is closed source.
If the big open source project was licensed under a copyleft license, I would have to make my tool open source as well. Then I would have a hard time selling licenses.
I couldn't have spent the last 10 years building a tool for the open source software, and users of the open source software would have had fewer tools available.
Your personal financial incentives < humanity. I would rather you had a harder time selling licenses if it meant the ecosystem around whatever big project you're talking about was compelled to contribute to the commons in the same way that the big project does.
Proprietary software is the dead or soon to die branches of the tree of human development, may spawn some useful insights that will ultimately be applied elsewhere, and may be profitable and useful in the short term, but the branch dies, I don't want to subsidize dead branches, and I don't want to write software that enables people to make more of them, even if some of those branches might be nice to hang on for a while.
I can sell licenses to my tool because it is closed source.
If the big open source project was licensed under a copyleft license, I would have to make my tool open source as well. Then I would have a hard time selling licenses.
I couldn't have spent the last 10 years building a tool for the open source software, and users of the open source software would have had fewer tools available.