News for hackers. Stuff that matters.

A comment on TerarkDB, ByteDance's RocksDB replacement. Parent comment

Re:TerarkDB, ByteDance's RocksDB replacement by setr on Wednesday December 23, 2020 @02:26AM (#25515347)
Sure it is; it’s exactly equivalent to something like forking Linux with the reasoning “I want to be the BDFL now” — eg the nvim fork
[ Parent | on HN ]
Re:TerarkDB, ByteDance's RocksDB replacement by haar on Wednesday December 23, 2020 @10:44AM (#25518729)
Wasn't the driver for nvim specifically disagreements with the direction/priorities/steer of the project? Is progress in a different direction necessarily a bad thing, especially if that effort couldn't be directly applied to the original anyway?

Please someone feel free to correct me, but if I recall correctly a lot of the improvements in Vim 8 were a result of the popularity of functionality in NeoVim?

[ Parent | on HN ]
Re:TerarkDB, ByteDance's RocksDB replacement by setr on Wednesday December 23, 2020 @05:14PM (#25522885)
You're correct -- which is why I've used it as an example of forking for project-control reasons to be perfectly in line with an open-source philosophy.
[ Parent | on HN ]
Re:TerarkDB, ByteDance's RocksDB replacement by ssakamoto on Wednesday December 23, 2020 @04:06AM (#25515836)
No disagreements there. Contention is it's not good for the original.
[ Parent | on HN ]