One thing I liked about liberally licensed libraries was that I could use and contribute to them both at my day job and my side hustle. If I wanted a particular

One thing I liked about liberally licensed libraries was that I could use and contribute to them both at my day job and my side hustle. If I wanted a particular library at my regular job and my side hustle, the lowest effort way to do that was to release something as MIT/BSD/Apache (and maybe MPL) on my own time, then use and improve it at my regular job, which meant I could avoid doing the same work twice (and maybe get coworkers to contribute). That just isn't feasible most of the time for Free Software. If you want to profit from Free Software, you have to design both the software and your business model around the license. With liberally licensed software, you just use it. And yes, it certainly benefits other companies, but is that really the bad thing? I'll work on something if it benefits me, and if it benefits someone else too, that's fantastic. I don't care if it nets me hundreds while netting someone else millions, I'm still getting hundreds. I used to build stuff to be "part of the community", but that's less important to be now than building stuff because it benefits me. There are a million projects I could involve myself in, so now I'm just a bit more selective on what I contribute to.