3 ms·

I'm not saying don't learn RocksDB - quite the opposite. It's a great tool to have in your toolbelt. I'm saying that unless you've used and hit the limits of R

I'm not saying don't learn RocksDB - quite the opposite. It's a great tool to have in your toolbelt. I'm saying that unless you've used and hit the limits of RocksDB - and it's already absurdly fast - there's zero reason to utilize this project. Maybe it'll mature one day, have multiplatform support and a wide array of client libraries, and be to RocksDB what RocksDB was to LevelDB. But today is not that day. For now, developers that don't immediately understand what this project is for would best be served with a simple link to RocksDB.

KingOfCoders 6y ago
And how should I know this from the README? How should I decide between a project that is interesting and not explained from a project that is not intended for me?
- ddorian43 6y ago
  > How should I decide between a project that is interesting and not explained from a project that is not intended for me? You first try rocksdb/lmdb, learn it all, break things, hit limitations, and lower your standards enough to search for other things, that don't have comprehensive documentation but just a small readme/paper and checking the code. Don't expect to build a better Postgresql on the first try.
- reitzensteinm 6y ago
  You're shifting the goal posts. You wrote the initial post saying they're hurting themselves by not being more clear. I don't think that's true. Now you're saying they should be more clear to help beginners in the field. I completely agree.
  - KingOfCoders 6y ago
    I was rephrasing my point because some didn't understand it the first time. It appears you are cherry picking and missresenting my post again. It had several points where the first point was about me as someone reading dozens of HN posts a day following links and needing to go on a googling spree to find out about a product I might or might not be interested in. The other point was about the missed opportunity to attract users. And even the second point used "projects" and talked about relase pages which made it clear that the it's about the generality of the problem (the linked page wasn't even a release page) Picking out the specifics you either haven't read the post or are misresenting it intentionally.

KingOfCoders 6y ago

And how should I know this from the README? How should I decide between a project that is interesting and not explained from a project that is not intended for me?

ddorian43 6y ago
> How should I decide between a project that is interesting and not explained from a project that is not intended for me? You first try rocksdb/lmdb, learn it all, break things, hit limitations, and lower your standards enough to search for other things, that don't have comprehensive documentation but just a small readme/paper and checking the code. Don't expect to build a better Postgresql on the first try.
reitzensteinm 6y ago
You're shifting the goal posts. You wrote the initial post saying they're hurting themselves by not being more clear. I don't think that's true. Now you're saying they should be more clear to help beginners in the field. I completely agree.
- KingOfCoders 6y ago
  I was rephrasing my point because some didn't understand it the first time. It appears you are cherry picking and missresenting my post again. It had several points where the first point was about me as someone reading dozens of HN posts a day following links and needing to go on a googling spree to find out about a product I might or might not be interested in. The other point was about the missed opportunity to attract users. And even the second point used "projects" and talked about relase pages which made it clear that the it's about the generality of the problem (the linked page wasn't even a release page) Picking out the specifics you either haven't read the post or are misresenting it intentionally.