Discussion I’ve seen on the subject on Hacker News tends to veer towards MIT being the only license allowed for use in many orgs (with exceptions of course) because license compliance is hard to manage when you’re using a lot of open source and you’re a small org. So many developers release their code with MIT licenses so it gets used more and looks better on the portfolio.
While I can see their perspective I personally agree with your take and would love to see more GPLv3 adoption and fewer stupidly permissive licenses. There’s tooling out there to help with the license compliance challenges, if enough developers moved away from MIT licenses then companies will be forced to deal with it.
Discussion I’ve seen on the subject on Hacker News tends to veer towards MIT being the only license allowed for use in many orgs (with exceptions of course) because license compliance is hard to manage when you’re using a lot of open source and you’re a small org. So many developers release their code with MIT licenses so it gets used more and looks better on the portfolio.
While I can see their perspective I personally agree with your take and would love to see more GPLv3 adoption and fewer stupidly permissive licenses. There’s tooling out there to help with the license compliance challenges, if enough developers moved away from MIT licenses then companies will be forced to deal with it.