Comment by OutOfHere
1 day ago
If I can't trust their first project (KuzuDB), then why on earth would I trust any subsequent project by them? I won't.
This is why I stick to SQLite or PostgreSQL when it comes to databases. An LLM can trivially write me the commonly necessary graph queries if I should need them.
My best guess is the company was acqui-hired and will soon be working on implementing Kuzu's tech in a different database owned by the acquirer.
My _hope_ is that it was some IP issue with the University of Waterloo and a new company will appear shortly and pretty much pick up where they left off, but that's probably just wishful thinking on my part.
Why does an MIT-licensed open source project owe you anything whatsoever?
How did you interpret this person comment as about being owed anything? It's simply a fact of life that it's not smart to put your eggs into an unstable basket.
It's not about what is owed; it's about what can be trusted. The people behind Kuzu have shown that they cannot be trusted to be used.
I don't see why. Every project periodically decides what features they will move forward with and what features they will drop. Some users will have built dependencies on those dropped features. That's their problem, not the software project developers.
Python dropped or changed a lot of things between Python 2 and Python 3, creating a lot of rework for a lot of users. Are they not to be trusted as a project? Is every project obligated to support every feature they ever released, forever, to be considered trustworthy?
To quote from the MIT license: THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND