A fair number of FOSS licenses were interpreted this way. The popular migration away from GPLv3 (might’ve been v4?) towards MIT, LGPL, etc had more than one cause (a huge one was the rapid sectoral commercialization; the decline of RMS’s reputation may have contributed, etc), but a big one was the potential interpretation of new GPL as being overly viral and “license-infecting” only slightly related software assets rather than wholly derivative ones.
For me, it's the latter: the GPL feels overbearing and patronizing, and I don't want some dependency to dictate under which terms I can release my own software. I pay the community back by using MIT whenever I open-source something. This feels more "free" than RMS's view of freedom.
I know that many people would disagree with me on this, but thankfully I'm free to choose what license I consider "free".
> towards MIT, LGPL, etc had more than one cause (a huge one was the rapid sectoral commercialization; the decline of RMS’s reputation may have contributed, etc)
This conversation has come up a lot, and I’m always amazed at how hard it is for people to accept that maybe the MIT license (and other permissive license) people actually want the MIT license terms and there’s no more complex reason behind it.
I’ve read so many rationalizations that frame it like GPL was the default or right choice and then something happened that made people defect away from it. Blaming RMS is common.
I think the more honest read is that people and groups decided that MIT matched their goals and decided to use it. Not that they defaulted to GPL and then found reasons to leave it.