People subscribe to Go lists because they want to discuss technical aspects of a programming language. For other topics, there are other venues.
Yes, and for highlighting off-topic subjects, there is the simple moderator acronym "OT". A rigid rule book and enforcement policy has nothing to do with free speech. It's all about trying to balance the inequalities in the tech sector. Unfortunately, a rule book is not going to solve that problem. The cynic in me just thinks this a conference "feel-good" announcement planned as a result of Googlers feeling bad about the fact that they are a 83% male workforce.
If the real problem is going to be solved, it's got to be about encouraging and educating people from all genders and races to code. That starts much earlier than any engagement in online communities. If the output of schools and colleges of trained coders was balanced, all the horror stories of harassment and abuse would soon become history as the workforce also becomes balanced, in my opinion.
I strongly dislike the idea of self-appointed judiciaries. Mistakes happen. The nuances of behaviour of people with mental health issues is likely to get caught up in these rule books. That's why we have courts, to help deal with difficult cases. Vigilantes may well refer to the code of conduct for justification for statements of intent like this:
The plastic which held them in place was always broken on the school computers :-)
In all seriousness though, I personally owe a great debt to Sophie Wilson et al for building computers and software that made it very easy to start programming the second after turning a computer on; A BASIC interpreter and an Assembler available instantly from ROM. I had endless hours of fun building parallax scrolling star fields by poking directly to video RAM and slowly rendering 3d scenes in Render Bender. It was just a shame that the computers were so expensive.
Read "Flash Boys" for a better insight into how much difference variable latency between exchanges and clients makes to the profitability of fast execution of trades.
Has the fork author discussed with Mikio the implications of forking and the need for a commercial license for proprietary applications?
It's a shame that development stopped on Kyoto Cabinet and Tycoon. I personally learned a lot about efficiently using on disk storage from the source code.
Thanks for the reply. Interesting that linear hashing had such a big effect, seeing as it is meant to be a slowly-occurring process that only happens when the average load factor of all buckets exceeds a threshold. I guess that was back in 2004 though. Wonder if the same performance is still applicable?
"We abandoned them in favor of B-trees in OpenLDAP 2.2 because extensive benchmarking showed that BDB's B-trees were faster than its hash implementation at very large data sizes."
Didn't bdb's linear hashing scheme extend the size of the hash table enough to keep it at the required loadfactor?
I was just about to make the very same suggestion. Ignore the list and just read this book! The threading of the 'jaunting' concept was way ahead of its time in 1956 and the inspiration can be seen in many modern films.
It was an example of a language feature, that is short variable declarations in type switches, which avoid repetitive casting. The example below has the default clause which handles unknown types. I suppose the point is that you'd never actually do any of this because the method is disgusting.
https://en.wikipedia.org/wiki/Birkenhead_Park#Influence