Is it an application the end user will use directly? In that case, GPL.
Is it an implementation of a codec, file format, or protocol you want to promote widespread adoption of? In that case, MIT. (I.e. FLAC, Webm)
Is it an application that runs on a server that end users interact with remotely? In that case, AGPL. (I.e. Mastodon / Lemmy)
I didn't really care until I read Drew Devault's take. Now I'm an (A)GPL zealot. Stallman can still get fucked though.
Drew never gets too deep into the theory weeds but I appreciate his willingness to sprinkle anti-cap radlib stuff into his writing:
If the people with their fingers on that button held these same ideals, we wouldn’t need the GPL. The reality, however, is that we live in a capitalist world. Our socialist free software utopia is ripe for exploitation by capitalists, and they’ll be rewarded for doing so. Capitalism is about enriching yourself - not enriching your users and certainly not enriching society.
Here's some bullet points.
If you use MIT, others will be able to fork your code without sharing their modifications.
