Why Go Was the Right Choice for CockroachDB (2015)
cockroachlabs.com
Why Go Was the Right Choice for CockroachDB (2015)
1–7 of 7 posts
Re: Why Go Was the Right Choice for CockroachDB (2015)
#2Needs a (2015).
Re: Why Go Was the Right Choice for CockroachDB (2015)
#3FYI, this was written in 2015. Can we update the title?
Re: Why Go Was the Right Choice for CockroachDB (2015)
#4[deleted]
Re: Why Go Was the Right Choice for CockroachDB (2015)
#5I would be interesting to do a comparison of bugs found / fixed in CDB vs TiKV [1] (written in Rust) to see how much of an impact thread & memory safety have.
Re: Why Go Was the Right Choice for CockroachDB (2015)
#6I would be interesting to do a comparison of bugs found / fixed in CDB vs TiKV [1] (written in Rust) to see how much of an impact thread & memory safety have. [1] https://github.com/tikv/tikv
Thanks.. now I have another rabbit hole to dig into... ;-)
Re: Why Go Was the Right Choice for CockroachDB (2015)
#7Coming up next - why Go was a wrong choice and Rust is the right one