"These are recurring issues that affect everyone who writes their tools in C"
@lupyuen Disclaimer: I'm not a C programmer. Can't the majority of these issues be solved with greater familiarity with the language? That's actually mentioned handwavy way later in the article. And the strtok() example feels particularly contrived. There are a lot of good reasons to avoid C, but this doesn't make the case convincingly
Since I don't use C much, maybe I'm missing it, but there's a lot of ways to royally mess up in "safe" languages too
@cypnk @lupyuen exactly. The language is not the problem, but the experience and common sense of the programmer is what makes the difference. Finding someone with these two characteristics nowadays is hard and that's why the trend on promoting safer languages which force you to follow better standards.
@lupyuen not wrong about the strings..