A year down the line, 20 companies are using your code. Two years down the line, 100 companies are using your code.
Now you have a choice: Do you continue donating your time, servers, emotions and experience to making someone else money?
If you choose yes, know that typically at least one of those companies will be hounding you for bugfixes or out-of-scope demands. We have seen how much the internet can vilify people who refuse to do this kind of free work. If your turnaround for a fix on your globally used code is anything more than minutes, you will be hated. At least, until it's fixed, then you'll go back to being ignored.
If you choose no, well you have two choices: Change the license and yank the rug out from under people, or pass it on to someone else - who might pass it on to someone else - who might pass it on to a scammer who breaks the whole internet. Either way, the internet will vilify you for twice as long for your choice.
Many people, especially with programmer brain chemistry, end up going down the high-momentum-low-friction route of burning themselves out for the sake of conflict (and bad reputation) avoidance. Because it's very easy for you to say "sell your product", especially if that's something you're good at (or if you've never done it before and so presume it's something you're good at).
So once you see that, and you know that, and you see fellow developers stuck in the same hole and you see that you are well placed to do something - anything - to help change that, wouldn't you?
> there is no expectation of being paid. If one expects to be paid, one should sell their product.
Like most blasé statements, this statement doesn't help anyone. Not least because that's exactly what Tea seems to be trying to help people to do. Whether they succeed or not, no idea - but I wouldn't be bashing the concept this early on.