4 ms·
This is a 114 page paper that describes the extreme details of squeezing every ounce of performance out of memory. While I agree every programmer does not need
by sqeaky 9y ago
This is a 114 page paper that describes the extreme details of squeezing every ounce of performance out of memory.
While I agree every programmer does not need to know, calling it vacuous without reading is deeply insulting to such a useful document.
I read every page of it some years ago and will likely re-read it again soon as details fade.
- savanaly 9y agoHe called the title vacuous. Big difference.
- sqeaky 9y agoIt is not important, but I would argue even that, at worst its dated. The success of this paper seems to be what kicked off the trend of "Everything about <blah> every programmer [needs|should] know". Just like I wouldn't consider the "Goto's considered harmful" title to be vacuous despite the endless parade of copycats with "<Blah> considered harmful" articles and papers.