> I prefer the MIT license for my own projects.
Yes, but it's a different license! It's not really comparable with regards to preference because the goal of MIT or BSD is different to GPL.
If $PROJECT-1 can be modified and then redistributed as closed-source by $COMPANY, then MIT is a good fit.
If $PROJECT-2 must only ever be redistributed if $COMPANY redistributes their modifications and derivatives as open-source, then GPL is a good fit.
It depends on the specific project, which is why I cannot say "I prefer MIT" or "I prefer GPL", because for some projects I don't want it repackaged and released as proprietary software, while with others I do want others to repackage and redistribute as proprietary software.
Proclaiming a preference for one type of license over another is akin to saying "I prefer bicycles", because you aren't going to prefer bicycles when needing transport to move house.
Yes, but it's a different license! It's not really comparable with regards to preference because the goal of MIT or BSD is different to GPL.
If $PROJECT-1 can be modified and then redistributed as closed-source by $COMPANY, then MIT is a good fit.
If $PROJECT-2 must only ever be redistributed if $COMPANY redistributes their modifications and derivatives as open-source, then GPL is a good fit.
It depends on the specific project, which is why I cannot say "I prefer MIT" or "I prefer GPL", because for some projects I don't want it repackaged and released as proprietary software, while with others I do want others to repackage and redistribute as proprietary software.
Proclaiming a preference for one type of license over another is akin to saying "I prefer bicycles", because you aren't going to prefer bicycles when needing transport to move house.