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".
Genuinely interested: why MIT and not, e.g. MPLv2?
MPLv2 is copyleft, but not "viral": so you can use an MPLv2 dependency just like if it was MIT, but if you modify it, you have to distribute the changes.
I genuinely don't see why anyone would need to be more permissive than MPLv2, except if they want to benefit from patching code they didn't write without contributing back. But I don't think we should encourage that.
RMS’s view of freedom is that devs should restrict themselves for the sake of the freedom of the users. AFAIK, that’s the explicit goal of the GPL.
> I don't want some dependency to dictate under which terms I can release my own software.
Then you shouldn't release it under the MIT license, which has restrictions and requirements on speech. You have to release it to the public domain. Pretending MIT doesn't dictate terms under which you can release your own software is just a fantasy.
From the developer's perspective the difference between those licenses isn't that big when you open source your stuff anyway.
But please don't forget about the users. Only the copyleft licenses guarantee (legally) that the user gets to enjoy the freedoms, too.