The only possible ways you can believe you can write issue-free large scale projects in C, which don&#x27;t suffer from all the usual pitfalls of C, are:<p>* You&#x27;ve never deployed one.<p>* You&#x27;ve never had to maintain one.<p>* You wrote the last line of code and handed it over to the maintenance team, who then never gave you feedback.<p>* You have no customers.<p>* You have done a never-before-seen formal analysis of a large scale project down to the individual source line level, and made no mistakes with the formal specification.<p>The author is correct: use C only if you must. There are still an enormous number of reasons why you <i>must</i> use C, but it should be a constraint imposed on you, and not a language you actively want to start a project in.