|
Near as I can tell, there’s nothing in this agreement that prevents me from choosing another license model. If I can choose to apply whichever license I want, then it would seem that The Commons Clause could only possibly harm those that choose it. Anyway, there are plenty of unprofitable licenses out there, and the reality is, for all of them, if you’ve already given something away for free, once the cat’s out of the bag, you probably won’t make any money, even if your license doesn’t say you’re a bad person for even thinking about trying. That said, The Commons Clause is probably fine for foundations, where lots of people are sharing an array of technologies, and not really asking for money. Meanwhile, it’s been several decades of HTTP over TCP/IP, and last time I checked, there isn’t a whole lot to lock down, and the real money is in adding reach to flip switches from the other side of a network connection. JSON isn’t going away, so, there really isn’t much to apply licenses to, in this area, without being silly. But hey, databases, operating systems, desktop applications, peripheral drivers, all these things still happen, so I guess there’s stuff to license. But really all the fringe licenses mostly get applied to JavaScript frameworks, and by the time you actually read a JS library’s license, three other projects have replaced it, so why bother. |