This is great. Someone should change the title so it's descriptive of what's going on, although I have no idea what that title should be, heh.
This post is about Github moving some code from ruby to C for performance, MRI's GC, and judy trie-like data structure and how it compares wrt to both performance and memory consuption with hash implementations.
I guess I still prefer a catchy title to preachy ones that extensively use RFC 2119 keywords. e.g. "Why you SHOULD profile Ruby code to catch expensive regex bottlenecks" :)
Comments
This is great. Someone should change the title so it's descriptive of what's going on, although I have no idea what that title should be, heh.
This post is about Github moving some code from ruby to C for performance, MRI's GC, and judy trie-like data structure and how it compares wrt to both performance and memory consuption with hash implementations.
"... I have no idea what that title should be, heh."
It's a reference to the Beatles' song, "Hey Jude" (which opens with "Hey, Jude, don't make it bad | Take a sad song and make it better ...").[1]
[1] http://en.wikipedia.org/wiki/Hey_Jude
Edited for clarity.
The issue is that the title, while clever, doesn't give a even a remote idea of what the post is about.
I guess I still prefer a catchy title to preachy ones that extensively use RFC 2119 keywords. e.g. "Why you SHOULD profile Ruby code to catch expensive regex bottlenecks" :)
Personal preference though.