News for hackers. Stuff that matters.

A comment on In-memory key-value store in C, Go and Python . Parent comment

Re:In-memory key-value store in C, Go and Python by pjmlp on Wednesday March 21, 2012 @06:24AM (#3733758)
This is typical in the Go community.

Usually the supposedly Go advantages are presented in a way, as if the same are not present in other languages.

[ Parent | on HN ]
Re:In-memory key-value store in C, Go and Python by dhconnelly on Wednesday March 21, 2012 @07:19AM (#3733848)
This is actually typical in most programming language communities that I've observed.
[ Parent | on HN ]
Re:In-memory key-value store in C, Go and Python by drivebyacct2 on Wednesday March 21, 2012 @12:20PM (#3735061)
The author is up front about there existing more optimal and performant designs for python and C but remarks that this is a fast, easy, naive implementation. Who here doesn't appreciate those qualities or who here hasn't worked on a team where there life would have been easier if that one guy had a little bit harder time screwing things up?
[ Parent | on HN ]
Re:In-memory key-value store in C, Go and Python by ootachi on Wednesday March 21, 2012 @01:21PM (#3735370)
Careful with that argument. The fast, easy, naïve implementation in Go is quite dangerous (not even memory safe), because he forgot to lock the map. Go made it easy to write an incorrect implementation of a key-value store...
[ Parent | on HN ]