3 ms·
if you wanted to say "C makes it possible/easy/likely to have memory errors", i wouldn't have said anything. you drug in "offshored code delivered by sweep sho
by sigstoat 5y ago
if you wanted to say "C makes it possible/easy/likely to have memory errors", i wouldn't have said anything.
you drug in "offshored code delivered by sweep shop consultancies", got a response, and then move the goalposts.
go away.
- pjmlp 5y agoI am not going anywhere. You were the one asserting that it only happens in sweetshops, hence my remark wasn't valid, thus I decided to broaden the scope of people failing to write C. Those mythical C developers that are yet to be found after 50 years searching for them.
- dzaima 5y agoUsing C is a tradeoff. I personally wouldn't write unsandboxed mission-critical code that has to interpret untrusted remote user input in C. But for anything that's not that, the freedom it gives over everything is awesome, and it makes many things possible to do trivially that would be nigh impossible in most other languages (at least not while keeping around any of their properties of safety). But, it is, in fact, possible for good developers to write incorrect C code. Noone's claiming that's not the case. It's just a lot less likely for someone who actually knows the language and the codebase.