The support structure is different if you go with the FSF - someone can takeover the project and big corps that use the code must contribute back. My take is, c

The support structure is different if you go with the FSF - someone can takeover the project and big corps that use the code must contribute back. My take is, choose MIT if u want to give developers convenience (and u don't care if you r flooded with request and lack of attribution). Or choose GPL and the FSF if you care about legacy, organized support structure and end-user value. I even think dual license GPL version / paid version is a better choice than just releasing under MIT...I feel sorry but this story keeps repeating itself, we've been at it for decades and people are just realizing that open source is pointless without organized support groups or monetisation plan that respects developers and users freedoms