Programming Shucksters

If you don't regularly program in either C or C++, you don't know shit about programming. Now, it might be true that that you do in fact program regularly in C or C++ AND still don't know shit about programming, but it's never the case that someone who rarely programs in C/C++ knows shit about programming, therefore the original statement still holds true.

>>19
You know that if the kernel took care of garbage collection, it would ensure that pages in a process' small heap (assuming a generational GC) would never get swapped (that, most of the time, is the reason of the poor performance of GCed languages).
Lisp compilers are fairly good at optimizing, and their GCs are pretty fast.
You can't really say that Ocaml is slow, since its only purpose is to be a fast ``functional'' language.
Java is notoriously a slow memory hog, mono is a known failure, Python is Python, and there are too many Scheme compilers/interpreters to say ``Scheme is slow''.

If we were to microoptimize speed and memory footprint, why don't we just program in assembly?