3 ms·
What a lesson in unintended consequences. The license is vague enough that Amazon & co can just lawyer up and ignore it. What are they going to do, sue Amazon?
by bodas 8y ago
What a lesson in unintended consequences. The license is vague enough that Amazon & co can just lawyer up and ignore it. What are they going to do, sue Amazon? Good luck.
On the other hand, it will definitely scare away users of their software who will be concerned that their CRUD app derives "substantial" value from it and is thus infringing.
- mrep 8y agoBig companies do not like vague licenses. I work at a big tech company and I was specifically told to not use any software under the WTFPL license (Do What the Fuck You Want To Public License) [0] because it is not explicit. [0]: https://en.wikipedia.org/wiki/WTFPL https://en.wikipedia.org/wiki/WTFPL
- paulddraper 8y agoOn the contrary, it is very explicit ;)
- greglindahl 8y agoWTFPL is acceptable to IBM, though. I bet that this new license isn't. It's radioactive.
- thrillgore 8y agoThis was my takeaway. Amazon is basically squeaky clean as long as they avoid modules but everyone else just using a module on a redis install for a k/v database? You're now subject to additional license fees. It's not as sexy as redis but Memcache has none of these license issues and would be sufficiently usable for k/v data where I work. It's not vaugely licensed either. Congrats Redis Labs, you played yourself.