> Source plz ? The dominance of permissive licenses in the industry (compared to GPL) and the relative non-impact of AGPL software. I can't think of many AGPL

> Source plz ? The dominance of permissive licenses in the industry (compared to GPL) and the relative non-impact of AGPL software. I can't think of many AGPL (or similarly licensed) projects that have similar industry standard status as react or tensorflow have in their respective niches. > It's free as freedom, not beer. I'm sorry I should have made this point more explicit I guess. Of course I am well aware of the double meaning of free, and that it relates to freedom in this context. My point is that yes, that freedom allows you to do and read things, of course. But what? In an (exaggerated, and not entirely fair) analogy, it would be like claiming/securing the right to wear clown shoes during coffee breaks in the office. Yes, it's a right you may not have had otherwise, and it will brighten up your day, but ultimately it won't change the material relationship to your employer. In the same way, being allowed to read, modify, and distribute software is not in itself a solution to this specific problem at hand here, i.e. the strategy of Fortune 500 companies, as a stand-in for capital to get free labor from OSS devs. (note the omission of the "F" in this case because again, for the most part, this will happen with open source work, but not so much with libre projects). ------- As an aside, I'm unsure how to interpret the tone of your comment, so just to clarify: please don't mistake this as an attack from me on AGPL and similar. I think they're better than nothing and I personally prefer contributing to strongly copyleft projects. But they won't be a mechanism that can have a similar impact on the software industry as widespread unionization had on employer/employee relationship a hundred years ago. I lived in the Ruhr Area in Germany for a few years and the impact was really impressive, quite hard to imagine it happening like this today... The conclusion of the podcast I linked above is that IT work (and programming in particular) has developed from something where the individual holds significant negotiation power (and thus individual choices matter a lot) to a market in which workers are essentially interchangeable (since they all work with the same tools anyhow) and thus individual choices like Marak's are relatively less likely to be effective. Of course I hope that Marak gets hired and paid accordingly asap, but following this argument, in the long run programmers (the non-glamorous term for anything to do with code) will have to organize and/or accept significant drops in their salaries.