@freemo >I will never contribute to a copyleft project,
I have little interest in contributing to a project that won't defend the freedom of my work, so I have contributed to copylefted projects, but never to pushover-licensed ones.

>I certainly never want to be limited with how I can use my own projects either.
I suggest never using other developers libraries and writing everything yourself, if you feel like you're limited by not holding all of the copyright.

>which is why copyleft has been dying out significantly in recent years and largely replaced with MIT and apache licenses.
The fact is it hasn't - there exists more copylefted software now then in the past and freedom is being defended better than ever before.

Yes, microsoft and others have tricked many new developers into doing gratis work for them and their buddies, by making it seem that MIT expat and Apache 2.0 has "largely replaced" freedom-defending licenses, so more and more people make the mistake of using those licenses.

If they could, microsoft would make it that you couldn't even select say the GPLv3 as the license on github, but instead they've settled for making it ambiguous if a project is GPLv3-only or GPLv3-or-later (proven to be intentional as they refused to accept commits correcting this issue).

>The trend of GPL to isolate itself and push developers away by punishing the very people who release under it is exactly why its dying.
In reality, the floating island of freedom is bolstering itself slowly but surely with only high-quality developers, rather than welcoming low-quality ones, who will turn around and make the software proprietary.