drfugly

Because then you have to control ALL of the memory, not just the data that you're interested in optimizing. Not to mention that (at least in the JVM) the gc is pretty tweakable, and the entire team may not need to know about all of the tweaks.

As a netbeans user but vim fanatic. I really like netbeans for project management, but vim is awesome for just manipulating text tons faster than you can with netbeans. Try the jVi plugin for netbeans to get that text editing power of vim with the project management features of netbeans.

Right, but there is also the cases where a nlg(n) quicksort for the most part is slower than the O(n^2) version in the real world. I wonder if current CS teaching is completely ignoring real-word performance.

Yes, that's exactly what I'm getting at. Or cases where multithreading an application may look like it's going to bring obvious performance gain only to see the overhead kill your performance.

Will do for the color scheme.

What I was trying to ask was: Should real world performance be more heavily weighed? I feel like right now all the CS curriculum focuses on is O() performance as the end all.

When you were in class, where you ever even introduced to the concept that sometimes it might be possible that O() notation might not tell the whole truth? I understand that for the most part you shouldn't have to worry about it, but shouldn't we still warn students about this?

Isn't there xmove for this kind of stuff?

At that early age I wonder how much CS specific training is going to be given. Also with IBM's current focus on not just being a tech company anymore I would dream that the education is a bit diversified.

Maybe having a specific goal to drive for will make it easier students and teachers to focus on a certain goal but I don't think that it'll make the students less able to switch tracks if needed.

Netbeans with the jVi plugin for my vim bindings is where it's at for me.