Of course, you can frame the debate the other way around, i'm just making the point that "permissive/restrictive" means very little in this context and what matters really as a question is "do you wish huge corporations to benefit from your free-software work and expand on it to develop their own business, without EVER contributing anything back"? If yes, choose MIT and you'll probably regret it like so many open-source maintainers. Otherwise, choose (a)GPL and you probably won't regret it (at least i've never met someone so far who regretted choosing copyleft for their works, but it may exist of course).
But for your statement about licenses, there is actually not much I can say to counter your arguments. I've followed the fight between Amazon and Elastic so you have very valid points. For the moment I don't think SnowFS will face the same issues given its current scope and target audience/market
This discussion sounds like they were afraid to build Snowtrack on top of git.
I'm not a fan of the names of git commands and some of the other details about it, but functionally it works well and is the industry standard. To avoid it because of the GPL doesn't seem right. There are many commercial tools built of git.
This is the reason so few VFX, graphics, and game devs use Git for anything that needs to version large binary files.
Git LFS can help, but it's not always the right solution.
https://fossa.com/blog/all-about-permissive-licenses/
Even the GNU project uses it that way:
https://www.gnu.org/licenses/license-list.en.html
You're right that "restrictive" is an unusual term in this context. The antonym of "permissive" is usually "copyleft".