With my limited knowledge, I prefer GPLv3 for most of the stuff I write. This is mostly because I would expect anyone enhancing the code to give it back.
I would not release something that I write with Apache or BSD. These are "do whatever you want" licenses and might bite back. The whole Redis + Commons Clause debacle(if I can call it that) happened because Cloud providers wrap Redis in their services and charge for that without providing anything back to Redis. This is the "do whatever you want" part of these licenses.
I have doubt if anything that I make will be so successful, but in case it is, I would either want to earn by it by keeping it closed source, try some other way to earn by keeping it FOSS, but surely would not want only the big corporations to earn through it.
Last point to cover my ass. I understand that the Apache/BSD are pragmatic licenses and probably the main reasons why Open Source has turned even companies like MS to consider opening up their stuff. Only GPL wouldn't have done that. But somehow as a user I would prefer the latter.
That is still the issues in some of the projects that I work in.
Team not knowing any version control properly is one of the most common issue that I find. Nobody knows about unit tests. Build systems and checklists would be something too alien to comprehend.
One problem that I found with Lineage without GApps (using microG) was that GPS was done for. I couldn't use any map application for navigation, nor book a cab using Uber (their web interface kept denying my payment methods), etc. There were times when I was at a tough spot with friends and family -- trying to book a cab but couldn't. Again, using Uber is sending a tracking signal but it's either that or paying 2x the amount to a local cab.
So google play services is the necessary evil that I have to keep using even after switching to Lineage. I'm back to using them again, but PlayStore and PlayServices are the only two google apps that I have currently. I try getting most of my apps from FDroid -- my filter for "good" apps is mostly how active the repo is, not great but it works.
I've moved my mail over to Fastmail, and looking alternatives to Google Drive (Backblaze B2 is one that I'm thinking of). The problem with all of these non-google alternatives is although they're only slightly inconvenient for me, they're almost impossible for my family to use (B2 for example doesn't have an app).
I would not release something that I write with Apache or BSD. These are "do whatever you want" licenses and might bite back. The whole Redis + Commons Clause debacle(if I can call it that) happened because Cloud providers wrap Redis in their services and charge for that without providing anything back to Redis. This is the "do whatever you want" part of these licenses.
I have doubt if anything that I make will be so successful, but in case it is, I would either want to earn by it by keeping it closed source, try some other way to earn by keeping it FOSS, but surely would not want only the big corporations to earn through it.
Last point to cover my ass. I understand that the Apache/BSD are pragmatic licenses and probably the main reasons why Open Source has turned even companies like MS to consider opening up their stuff. Only GPL wouldn't have done that. But somehow as a user I would prefer the latter.