News for hackers. Stuff that matters.
Re:A critique of "How to C in 2016" by kbart on Friday January 15, 2016 @08:03AM (#10909027)
"Why on Earth would you voluntarily code in a language where people can debate something as simple as which type to use for integers, unless you absolutely had to?"

Because we have no alternatives so far. I do C programming for a living, but I'd be more than happy if there were some type and memory safe language I could use to program any tiny, obscure MCU, that could stay at least in the same order of magnitude of speed and let access hardware easily. Rust might be a step in a right direction, but it still has a looong way to go to become a viable alternative to C in embedded world. Of course, for a modern, high level development (web, mobile etc.), I see no reason to use C (maybe except for tiny libraries or co-routines where speed is critical). C is simply a tool -- it's neither good, nor bad -- and as every tool, it has it's use. You can easily break your fingers with a hammer, but that doesn't mean that it's a bad tool for driving nails in.

Re:A critique of "How to C in 2016" by briansmith on Friday January 15, 2016 @05:57PM (#10912912)
What do you think Rust needs to do to become viable in the embedded world?
Re:A critique of "How to C in 2016" by kbart on Monday January 18, 2016 @01:38AM (#10922916)
Ecosystem and community. Most of the time you can find what you need in C already written, in Rust it's do-it-yourself now.
Re:A critique of "How to C in 2016" by oldmanjay on Friday January 15, 2016 @08:26AM (#10909121)
You're aware that "we have no choice" does not answer a question about why you would do something voluntarily, right?
Re:A critique of "How to C in 2016" by kbart on Friday January 15, 2016 @08:34AM (#10909165)
I just confirm, that majority of C programmers nowadays do that because of "they absolutely had to".