In a similar manner, democracy is far more strict than anarchy because you can't kill and loot whatever you want.
Yes, I'm comparing murder and theft with taking away users' freedom. Yes, murder and theft are probably considered worse than proprietary software in the eyes of many. My point is that just because something is more restrictive, doesn't in itself make it worse.
If you have to redefine the word "FREE" to mean freedom and your license is several pages of lawyer speak, then that is a problem.
I will take anarchy over crazy ideology any day of the week.
GPL doesn't restrict how you can release your own source code - even if you release your project as GPL, you can still release it under MIT, or a commercial license - it's your code, and you're the copyright holder. The restrictions only apply to code derived from other GPL projects, but that isn't really "your code".
Your reason for avoiding GPL seems to be that you cannot take GPL code and release it under a non-free license. That's exactly the behavior that GPL is designed to prevent - the bottom line is users' freedom, not developers' convenience.
However, the relevant perspective on the GPL is that it's not really about freedom for developers. It's about freedom for users. If I as a developer/company want to ship modified FOSS to end-users. I can't hold the modifications back as secret sauce.
Translating this to the world of software licenses, similar things happen. With MIT, and BSD, an entity can take the project and just run with it. Neither the original owner, nor the ecosystem benefits. This is cool with some people, in theory, but from time to time, significant regret is demonstrated, of which my favorite is Tanenbaum learning from the media that Intel uses his system in all of the CPUs.
https://www.tomshardware.com/news/minix-creator-letter-intel...
I also recommend contemplating the "Paradox of tolerance" - a similar situation. It posits that in order to have a sustainable tolerant society, one must not tolerate intolerance - for if we do, it will take over, ending the tolerant society.
You can modify somebody's GPLed code and start selling it. The only restriction is that you must offer to share your source code with your customers and give them all of the same rights you have under GPL.
There is also a loophole that lets you sell modified GPLed code without sharing the source or giving them your GPL rights: run it on a server. AGPL closes this loophole which is why it is unpopular with large tech companies.
Any license that prohibits selling modified versions of somebody else's code would, if it became popular or was adopted by a popular project, be denounced by both FSF and OSI for violating the principles of the FOSS movement because the right to sell other people's FOSS software is considered an important user freedom. Writing such a license involves making fairly trivial changes to MIT or BSD but does make it impossible to combine any code licensed under it with GPLed code.
Someone can absolutely do that. They just need to share the modified source code.