Linked by Eugenia Loli on Mon 10th Oct 2005 16:48 UTC, submitted by Shlomi Fish
General Development Shlomi Fish has written a new essay titled "When C is the Best? (Tool for the Job)". Its theme is giving several reasons (besides high speed and low memory consumption) why some code should still be written in C.
Thread beginning with comment 42945
To read all comments associated with this story, please click here.
Improve C
by on Tue 11th Oct 2005 01:00 UTC

Member since:

Obviously the author doesn't know enough about Java to compare.

Lets face it. Java, Python, etc, are high-level languages and are doing a great job in this domain. They help developers get the job done fast. Of cause there are always room for improvement.

As for low-level languages the picture is a lot worse. Basically C is the only well supported choice (C++ is just a joke IMO). Now C is really a pain when you want to do larger projects. It was never designed for this. Despite this, a lot of hacks (preprocessor, automake, autoconf...) have made it possible to do larger projects.

SUN did a cleanup of C++ and made it usable high-level language (Java). This is really what C needs. It needs a cleanup that makes it a modern low-level language. While doing so a lot can be learned from Java, etc. I.e., I would like to have the compile speed of Java (yes it is fast when you subtract WM overhead. Look at Jikes). Also, Java has given us a lot of performance improvements that might be of use in a low-level language.

My point is that high-level languages have seen a lot of improvements in the last decade while low-level languages haven't. D is an exception, but IMO its target is too wide. It's not focusing on being low-level. Please tell me if you know other projects that are serious in improving the low-level language situation. I might have missed something...

Reply Score: 0