This, to me, gets into the difference between theory and implementation. I agree that understanding the theory behind memory management can be useful. However, learning malloc goes beyond theory into a specific implementation of the principle. In a garbage collected language, knowing the theory is potentially useful, but knowing how C's implementation works is not.

Why do CS PhDs, who spend 98% doing theory (math), need to know anything about installing an OS? Why do undergrads, who probably use preassembled OEM boxes, need to understand the differences between hardware brands? More to the point, how does learning memory management or class design through C++ help one learn these things? To address a less ridiculous point, if I'm spending all my time in Java, Ruby or Python, why do I need to understand anything about pointers and memory management in C? For the sake of argument, let's say we need to understand how the stack, heap, and reference variables work in a garbage collected language. Why do we need to learn C to do that? In undergrad I was required to take a class which involved writing one's own implementation of malloc. Like so many other classes required for a CS degree, I use nothing from it in my day-to-day work as a Ruby developer.

I have a Samsung RF510-S02 and I can't find the SL folder in my Windows directory.

Is anyone really reading this and scratching their heads, saying, "Well gee, I thought it was a bunch of intrepid hackers who broke into the mainframe to steal the pix?" Of course Apple orchestrates their leaks and rumors. Even their litigious cease and desisting of Mac rumor sites is all part of cultivating their mystique. Even "non-evil" companies like Google pull shit like this. It's all part of the marketing game to build pre-release buzz for products.