[Philipp__]

I like this blogpost. But as stated in it, “my project”. Writing C project, alone is pretty different than writing C with 1 or more persons.

In highschool we had group project. Writing simple tcp/ip protocol in C. Holy shit did I see some awfull things... maybe writing C is not the bad thing about it. But maintaining could be.

Simple example, you can read string from simple data file on 6,7 different ways. Yet their effects and behaviors differ severely. Not everyone knows difference in parameters and returns in scanf, fgets and gets...

[loeg]

I think your experience writing C with a group might be severely colored by the group being made up of inexperienced highschoolers.

[Philipp__]

I totally agree with you on that. But the whole point was that there is much certain possibility for things to go wrong with inexperienced developers. I won’t quote the comment in the reply below, but that is the thing...

edit: typing on the phone, sorry

[loeg]

In my experience, turning an inexperienced C developer loose with C++ does not result in an improvement :-).

[tomsmeding]

The thing with C is that there are plenty people that can code C and know what they're doing, but there are many more that either do not know what they are doing, or don't but think they do (which is even more dangerous). My experience mirrors yours, but I do believe these good C programmers exist.

[kqr]

I'm slowly starting to believe that every single C programmer falls into the "either do not know what they are doing, or don't but think they do" category.

I have yet to see a single, non-trivial C program that does not have many dangerous bugs related to language unsafety.

If these mythical good C programmers exist, they certainly have never released any of their source code.

[pjmlp]

It is like the driver paradox, when asked everyone asserts they are the best drivers in the world only the others are not.