Convince me

Convince me why I should use C over Java.

>>1
"Why?" is a useless question. "When?" is a better one. If you're writing a daemon that runs indefinitely and churns through a lot of data for every incoming connection, there's probably no reason at all to pick C over Java. However, if you're writing a  frequently invoked command line tool that needs to launch and finish its task as quickly as possible, anything on the JVM is outright disqualified, whereas (ironically enough) Ruby or Perl might be as good a choice as C.

If you hope to be a good programmer you should learn all of these and know their weaknesses.

>>25
There are lots of good reasons to pick C in the case you've presented. For one you can prove that what you wrote is correct, which is extremely important for what I'm currently working on. Incidentally, it's a series of daemons that will be invoked multiple times and then kept alive while a controller load-balances incoming connections over them. Very microkernel-esque.

>>29
I have to agree. A strongly typed language is invaluable when doing any kind of data processing. The compiler should go as far as running tests on your code to prove its correctness. Java simply doesn't give you that kind of guarantee.