News for hackers. Stuff that matters.
Re:The Resurgence of C Programming by jstewartmobile on Tuesday December 27, 2016 @03:09PM (#13265811)
In the commercial space, devs already have to rework their apps frequently to handle the curve-balls MS/Apple/Google etc. throw at them. If we had a C compiler with webkit-level dominance, and we made just one fix to it every cycle, that would be a big thing, and it would be manageable!

It's like, "Oh, to be C-2016 compliant I've got to get rid of all my calls to unsafe string functions." Search, replace, and some elbow-grease later, and I've improved my program with a much lower likelihood of breaking functionality.

Re:The Resurgence of C Programming by stymaar on Tuesday December 27, 2016 @05:23PM (#13266725)
> devs already have to rework their apps frequently to handle the curve-balls MS/Apple/Google etc. throw at them. If we had a C compiler with webkit-level dominance, and we made just one fix to it every cycle, that would be a big thing, and it would be manageable! It's like, "Oh, to be C-2016 compliant […]

Fortunately, the web doesn't work the way you think it work ! JavaScript written in 2005 is still working nowadays, and «not breaking the web» is the main reason JavaScript is so quirky. And the backward compatibility story of Microsoft Windows over the last 30 years is one of its bigger success.

You can't just expect people to rewrite their whole code every now and then … And if you do, people just stop updating or even drop your platform.

Re:The Resurgence of C Programming by jstewartmobile on Tuesday December 27, 2016 @05:41PM (#13266868)
Both Windows and JavaScript do break things, regularly. Small stuff, but stuff, and worst of all, it is usually in the service of some internecine pissing-contest instead of an incremental approach towards "better."

If we did the same thing with C, but with more high-minded goals, it would be a fine investment in the future.

Re:The Resurgence of C Programming by pdimitar on Tuesday December 27, 2016 @03:23PM (#13265909)
Since I am no longer heavily invested in the C/C++ stack I have no choice but to agree with you.

My general point is that IMO the tech giants' patience towards C's persistent problems is long over and that's why we have Golang, Swift, Rust etc. Don't crucify me for the "persistent problems" thing please. ;)

I fully understand the need for a language as close to the bare metal hardware as possible but many people -- me included -- prefer a more stable and predictable environment with the price of less speed.

I believe there's no right or wrong side in this particular preference.