Earlier quoted context omitted.
If you read me as saying making and selling proprietary software was wrong, you read a very different text from what I wrote. Making and selling software is perfectly fine, and building that software on top of libraries specifically released for that purpose is equally fine. Open source licenses that in perpetuity lock you out of any form of gains from your own work , even when that work is the very backbone of someo…
I believe the parent is responding primarily to this point: > The idea that you just mark your work as MIT/GPL/CC0 may have made open source more popular, but it also ruins lives when that thing you worked on for years and never made you anything makes a random drive-by asshole more than your annual salary. There's no reason this should ruin your life - your quality of living didn't suddenly decrease. If you are unha…
I won't fault them for expecting to get paid if they later realize the value of their work and know that it is generating significant commercial money. It is natural to feel like being taken advantage of by the commercial entity when they don't get compensated (even if that was their initial choice).
When someone says "you should have chosen to make it proprietary or use a more restrictive license from beginning", it might come across as a polite way of saying "Too bad, no backsies! You were foolish enough to chose a permissive license. So, accept the consequences".
If a developer wants to get paid for their work with something other than "feel good OSS points", I don't see many options out there. They need to solicit donations(which doesn't have good track record) or re-license.
I think as more products go through this cycle of permissive license, monetization by third-party and re-licensing, we'll be seeing a significant number of projects erring on the side of caution and use restrictive licenses from the start.