Fairly intersting viewpoint, although disagree with the author (if I interpret the post correctly, English is not my native language). Just ignoring any "ethica

Fairly intersting viewpoint, although disagree with the author (if I interpret the post correctly, English is not my native language). Just ignoring any "ethical" view point (because they are subjective and hard to agree on) and looking just at the practicality of the idea: > the danger is a mess of unenforceable licenses whose prohibitions become impossible to keep track of This is imho the most important part; once you start using basically personal license (I mean, each developer (person) has different set of values; some would be fine with military applications, some not; some would be fine with non-profit (doctors without borders) using their code, some would not), it becomes basically impossible to be sure your code is compliant or not. Once you realize that your would need to basically evaluate every single license in the dependency tree in depth (since they are basically non-standard, personal licenses at this point), it turns into insane amount of work. And expensive, since it would probably needed to be done by a lawyer. The split between gpl2, gpl3 and apache 1.0 and 2.0 is bad enough already.