Comment by SoftTalker
4 months ago
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
Huh. Your examples are not relevant because they do not apply to killing a project altogether, let alone to killing your very first project. Kuzu did both.
They tried something hard and it didn’t work out. In the process they did some great work. Plus they gave it all away for free, allowing literally anyone in the world to continue the work. They are awesome.
If the rest of us criticized people making open source like you do, there wouldn’t be any.
That's not how open source adoption works. For open source to get used, people have to trust that it will be maintained. The people behind Kuzu ruined any trust in them. This is also why people prefer established choices over the fashion of the day.
2 replies →