Note that AGPL does not actually protect your software from big companies (or small companies) running your software as a service. It requires them to contribute back or make source available when they make changes, and IIRC thats to the user (who could be an enterprise customer under some other agreement even, but none of this is tested in court).

If you want that sort of protection, BSL, SSPL, Elastic license, etc are what you want.

If you want to make Free Software, make it. Know that people you don’t like may use your software, even criminals may. That is what Free Software is. OSS is slightly different but similar.

If you want to make shareware, make shareware — no judgements on people who want to make money with their software and believe thats the best path.

I'm fine with big corporations use my software: the deal is that whatever they do with it, they must give it back to the users with the same license. Make it live beyond the company's existence and control. It's still better than my software being non-copyleft and being used by a company.

I wish they would give back all the profit as well but that's another topic and the AGPL doesn't touch that.

> AGPL is also the license you should use if you don't want big corporations to use your software.

Don't know about "big corporations", but in academia most people use Overleaf to share the editing of LaTeX papers, and it's AGPL software. In my lab we collaborate with many industrial partners, and they see no problem using that software either. We bought a quite expensive lab-wide license for Overleaf so that we can use more resources of their online offering. I have a friend at google who also uses it (but it's just a single data point).

I honestly don't understand what you are talking about.