Just trying to teach them that somewhere, down under all that runtime, there's a bunch of hardware which deals with the world 32 bits at a time, and that in the end all these magical "objects" really cook down to a bunch of memory addresses... yeow.
That's what I loved about being in computer engineering. You'll sit there and fill in charts of the cache, perform Tomasulo scheduling by hand, and by god at the end you'll have a pretty decent idea of how the machine does things. Not to say that CS students can't or don't learn the same thing, just that the ones I knew tended not to.
Re:The Book That Every Programmer Should Read
by nobody31 on Monday October 31, 2011 @06:18PM
(#3179384)
But you don't need all that stuff any more - you have garbage collection !
Re:The Book That Every Programmer Should Read
by dustingetz on Monday October 31, 2011 @03:06PM
(#3178567)
yeah, but the ones who actually care about CS probably do know most things covered in CODE.
I'm still trying to teach some of them that a memory copy isn't instant.