Errr. You do realise that your arguement reads a little as if you're are saying that that the automotive industry is in the ascendant whilst the oil exploration and pertrochemical industries are in decline? I'm not expert in rhetoric, but I belive that this sort of thing is called a false dichotomy (real rhetoric experts, feel free to jump in). One might make a similar arguement that most modern fashion challenges don't benefit from working on the level of textile design, or for that matter, growing cotton. Well, perhaps on a very narrow level indeed, but it does seem rather silly to mistake a desirable outcome for the reality of how it is achieved. I appreciate that I am somewhat misrepresenting your core point to leap into the discussion, but it is really quite impossible to not get a little peeved about these holy language wars which seem to break out at the drop of a hat (there is a post somewhere else in this article where someone states that they "hate assembler snobs", which makes about as much sense as hating farmers if you value being able to eat).
Look, as many others have pointed out, the whole point of computers, as viewed as a universal machine, is that you, as the programmer, get the damn things to churn out perfect copies of what you have told them to do, once, twice, one hundred, one million, tens of trillions of times. There has never, in human history, been anything close in terms of amplifying effort unless Archimedes himself has been elevated to some celestial plane where he does indeed have a long enough lever. That said, whilst people are thinking themselves smartarses for writing stuff in Java (the only language which is quicker to write than to run), then
a) the point is being missed, a bit, and b) best that other smart people look for better, faster ways of making stuff work.
Oh, and in the day job, 'C' is very much a high-level language. It is fine and, most importantly, portable for the purposes required, but our stuff simply would not work without breaking out the dreaded assembler here and there (there is tons of Java too, but we prefer not to speak about that). So what? The appropriate tool for the job and all that. The IT world truly amazes me. Do we really imagine that "news for plumbers, stuff that matters" would have long debates about the superiority of the spanner over the sink plunger? Some languages are perfectly fine for applications where the end user has all the processing power they need on their desk. Other stuff has to play nicely in a multi-user, multi-tasking, multiprocessing environment, and there it is best to use (and if it is important to you) learn the appropriate way to get the best out of that. Of course some commentators have a bit of an agenda here - I know and am familiar with language x, so it's the best thing since sliced bread and everyone should bow down to my incandescent genius - but that's bollocks. All it does is give the rest of the world the impression that this is a long way away from being even close to a profession; something which is very much encouraged by the common perception of the industry here in the UK (but you already knew that by the way I spelled "arguement") - stories of large systems developments going expensively tits up are ten a penny. Whilst it appears that the basic values in our business remain "x" is better than "y", then I don't expect that to change real soon now. Which is a pity; the world is at our fingertips guys (and gals). About time we take a leaf (only the one, mind) out of the book used by lawyers, doctors and other sundry self-serving trades and stop pissing on our own fireworks for a change.
Just my $0.02