Re:How this database legal war could be decided by the name ...
by db48x on Sunday February 12, 2023 @12:19PM
(#34764639)
The real problem is that they picked the AGPL, which has the Further Restrictions clause. If they didn’t want that, then they should have picked something else. They could have created a custom license, but instead they proudly announced that they were choosing the AGPL, and they gained significant goodwill from that. This lawsuit demonstrates that they are either incompetent, or that they were attempting to use the AGPL in a fraudulent way.
[ Parent
| on HN ]
Re:How this database legal war could be decided by the name ...
by toyg on Sunday February 12, 2023 @01:12PM
(#34765171)
Neo4J have a genuinely interesting product but they managed, throughout the decades, to hamper its adoption at every turn.
Re:How this database legal war could be decided by the name ...
by db48x on Sunday February 12, 2023 @03:59PM
(#34766873)
I know virtually nothing about the software, but I keep hearing over and over about the licensing problems. I doubt it’s the reason they want people to remember their name.
Re:How this database legal war could be decided by the name ...
by Spivak on Sunday February 12, 2023 @05:14PM
(#34767689)
Yeah, if money and time is no object graph databases are a joy to use but being a commercial database is pretty much the death knell for support in different languages and frameworks.