Badger – A fast key-value store written natively in Go
open.dgraph.io
Badger – A fast key-value store written natively in Go
1–10 of 101 posts
Re: Badger – A fast key-value store written natively in Go
#2Re: Badger – A fast key-value store written natively in Go
#3How do I use it? there is zero docs on how to even get started, what the API is like(is there even one?) This could be worth all the peanuts in the world, but if the only way to learn how to use it, is read the Go source, very few people will bother.
Re: Badger – A fast key-value store written natively in Go
#4How do I use it? there is zero docs on how to even get started, what the API is like(is there even one?) This could be worth all the peanuts in the world, but if the only way to learn how to use it, is read the Go source, very few people will bother.
Re: Badger – A fast key-value store written natively in Go
#5How do I use it? there is zero docs on how to even get started, what the API is like(is there even one?) This could be worth all the peanuts in the world, but if the only way to learn how to use it, is read the Go source, very few people will bother.
Re: Badger – A fast key-value store written natively in Go
#6Re: Badger – A fast key-value store written natively in Go
#7There's that word again, natively. Should just say written in Go. The native part is redundant.
I agree 'written purely in Go' would have been a better choice of words, though.
Re: Badger – A fast key-value store written natively in Go
#8How do I use it? there is zero docs on how to even get started, what the API is like(is there even one?) This could be worth all the peanuts in the world, but if the only way to learn how to use it, is read the Go source, very few people will bother.
https://godoc.org/github.com/dgraph-io/badger/badger#example...
Re: Badger – A fast key-value store written natively in Go
#9Re: Badger – A fast key-value store written natively in Go
#10There's that word again, natively. Should just say written in Go. The native part is redundant.
I believe the author is using the term 'natively' here to describe the project being written purely in Go, rather than using CGO (i.e. being a wrapper to some database written in C). I agree 'written purely in Go' would have been a better choice of words, though.