News for hackers. Stuff that matters.
Re:How to C in 2016 by csvan on Friday January 08, 2016 @07:16AM (#10864324)
"The first rule of C is don't write C if you can avoid it."

This ought to carved into the walls of R&D departments everywhere.

Re:How to C in 2016 by jballanc on Friday January 08, 2016 @07:42AM (#10864444)
"The only bug free code is the code you don't write."
Re:How to C in 2016 by jandrese on Sunday January 10, 2016 @11:50AM (#10875939)
If you think the third party library is bug free I have news for you. The only difference is that you get to debug someone else's code instead, and you might not have the source.
Re:How to C in 2016 by chrisseaton on Friday January 08, 2016 @07:37AM (#10864420)
Why do you think R&D departments use C more than anyone else?
Re:How to C in 2016 by qntty on Friday January 08, 2016 @10:15AM (#10865390)
I think the implication is that R&D departments have the control to avoid it