I have to use C because the hardware I use at my company requires it for a number of reasons (performance is not one of them). C was my first language and it is

I have to use C because the hardware I use at my company requires it for a number of reasons (performance is not one of them). C was my first language and it is responsible for a very substantial part of my income. But I find the establishment of C and intel arch the reason you still have to use a keyboard chip to enable 32/64 bit mode in a computer: https://github.com/eduardordm/sisop/blob/master/sisop.asm https://github.com/eduardordm/sisop/blob/master/sisop.asm (see line 110) C can be low level, but it is mainly a high level language and it will 'distort' programmers just as any other language. Just because it doesn't have simple features it doesn't mean it is closer to the hardware. C teaches you how to destroy memory, not manage. malloc+free are most harmful functions of the history of computers. (and I don't think I'm exaggerating) You can actually evaluate how awful a C programmer is by counting the number of mallocs/frees he uses. Oh, I don't like C, by the way. (but I'm really grateful for knowing how to solve problems using this handicapped tool)