It is amazing that the people who rely on high-level languages think they can stomp on lower-level languages like this, without even realizing that virtually _all_ the features they talk about are made possible by low level languages and are implemented in them.
New C programs get written all the time. They work. They move your world, every day, like clockwork.
At least with Java, pointers/references/objects are either null, or valid. Uninitialized references won't compile, and a null dereference blows stack at point of first use.
Having said that, I like pointer and bounds checking, but wish Java had significant memory management options, for times when you were willing to trade some safety for speed.
A segfaulting program will dump core, which the programmer can use to get the stack trace. I consider this to be better UI than printing the trace at a likely bewildered user.
$ ulimit -c
unlimitedSounds like a feature.
C allows you to write interpreted languages that execute with a speed high enough to afford you more abstraction.
Let's give credit where it's due, but really C could have been Ada in any of those examples and the results would have been about the same (especially in PHP's case).
This is straightforward enough in C: http://gaiustech.wordpress.com/2011/09/09/segmentation-fault...
$ ls -1 git-*.sh | wc -l
25
$ ls -1 git-*.perl | wc -l
9
Compare this to the built-in commands: $ ls -1 builtin/*.c | wc -l
92
or all the C files: $ git ls-files '*.c' | wc -l
306
The real reason that most C programs in daily use are so robust, is because they are ages old. Many, many man-years have been invested in the production of e.g. BSD, unix tools, POSIX libraries, and even web browsers and word processors.
Why do we use Javascript and even PHP to program web-applications? Because we need fewer lines to get the same result. Moreover, given the correlation between number of lines and number of bugs, shorter programs are better. If we had been limited to C "web 2.0" would have been decades away.