News for hackers. Stuff that matters.
Re:A critique of "How to C in 2016" by pjmlp on Friday January 15, 2016 @05:57AM (#10908463)
See, that is the problem right there.

Even if one does find such competent programmers, I doubt they the way C culture works it would help.

Most C devs I have met, if given a memory safe systems programming language like Modula-2 or Rust, would just use SYSTEM or unsafe {} everywhere without any proof of a profiler if it really matters to the customer.

As for being available everywhere, that is an historical accident of C's adoption. I remember when C was only available in UNIX and we had things like RatC.

Re:A critique of "How to C in 2016" by EliRivers on Friday January 15, 2016 @06:51AM (#10908675)
Slightly off-topic, I'd say that the majority of programmers, C devs included, are barely competent. They know enough to bash through to something clunky and dangerous that kind of does what's needed at a demo. Whilst it's true that taking away all the dangerous tools would make it harder for this great sea of perpetual amateurs to do so much damage, I think it's not right to blame the tools.

By simply being here and reading this, you're almost by definition in the top 20% of programmers. Hyperbole, yes, and counter-examples exist, but anyone who routinely comes here will improve; the majority of programmers never do.

Re:A critique of "How to C in 2016" by omgtehlion on Friday January 15, 2016 @06:37AM (#10908614)
heck, even in c# I use unsafe{} here and there ((
Re:A critique of "How to C in 2016" by NoGravitas on Friday January 15, 2016 @02:49PM (#10911630)
))
Re:A critique of "How to C in 2016" by mchahn on Sunday January 17, 2016 @02:56AM (#10918742)
;