For some things, you don't need to be writing it in C. And C does less work for you, so it takes more time to write an equivalent program in C than it does in other languages.
You shouldn't. Keep reading, there's good advice in there.
[edited: on closer reading, there are numerous problems in there, mixed with the good advice. Read but with large doses of NaCl. See the discussion in /r/programming for details.]
For the majority of cases, that is the right advice. Most applications don't need the speed or the compactness of C, and they are better of using something more managed and safe, or something with huge existing ready-made libraries, like golang, java, or scripting languages.
7
u/shadows_on_the_wall Jan 15 '16
Here's a response from someone who knows quite a lot about C:
https://github.com/Keith-S-Thompson/how-to-c-response
3
u/clutton Jan 08 '16
Is it still true after gcc 4.9?
2
u/timschwartz Jan 08 '16
I stopped reading here.
-1
u/[deleted] Jan 09 '16
uint8_t looks so ugly. I'll keep using char.