- Joined
- Feb 9, 2013
Then I'd have to ask you in response: why would the fact that network drivers are written in C mean that it's not irresponsible behavior?what does it have to do with anything? You stated network facing code in C was irresponsible, regardless of how much of it is written in a given year.
This wasn't my intention when I originally said it, but the market popularity of C for network code might have an indirect relationship with how good of a decision it is, because shitty C code is driving developers away from using it.
Kind of a meaningless benchmark, considering how loosely defined "the result of the compilation of C code" can be.And as a volume of code shipped, most of the volume is the result of the compilation of C code.
Definitely not. Code written by humans is substantially different than code written by machines.Code use matters more than code writing.
One could argue that C's popularity is a historical accident in some ways and not because of any merit inherent in the language.C is the lingua franca of programming. It's importance cannot be taken lightly. You cannot do serious programming without using it to some extent.
There are alternative execution models and languages at every level of abstraction. From bare metal, all the way up to high level stuff. (An example of an interesting low level alternative to C is Forth.)
I mean, C's in place in many areas, and you might as well use it if it fits your use case (and you keep the interaction with humans to a bare minimum). But arguing that C is "good" is not the foregone conclusion many seem to think it is.
And it's not really the lingua franca that you make it out to be. In many situations, it's basically used as a proxy for x86 calling conventions.
Last edited: