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.
Permalink for comment 42654
To read all comments associated with this story, please click here.
Huh??
by Anonymous on Mon 10th Oct 2005 17:18 UTC
Anonymous
Member since:
---

Its pretty obvious that for low-leveled stuff, integrability, and speed/memory consumption, C is best. All the other reasons are almost specific to Java (and/or mono/.net). So basicly he is reiterating the first well known reasons.

Then he comes and brings an example from his own program and why he would be uncomfterble using anything else. Then he goes and assumes how in every other no-C language it would be slower without even proving his claims. I actualy think that it would of been interesting to see an actual comparison between his C program and another implmentation in some compileable functional language. Well, that is if he would of actually DONE some comparison.

Last, who the heck ever argued with this article? Infact, afaik, in the python community it is a well accepted paradigm to write some time critical code in C and then add it as a module to the rest of your program. Heck there have been quite a few commercial games that had thier game engine written in C and everything else written in python (like implementation of the different units, map scripting, etc...)

Reply Score: 2