C considered dangerous
C considered dangerous
Posted Aug 30, 2018 22:50 UTC (Thu) by marcH (subscriber, #57642)Parent article: C considered dangerous
tl;dr: for safety C is broken beyond repair. As a meta-assembler it was a "stroke of genius" but it just can't scale beyond that.
> https://raphlinus.github.io/programming/rust/2018/08/17/u...
> > If one’s interest is in safe, portable code – C can be a very fine choice. One must use it well, though [...] C’s sharp edges can be managed safely two ways, at least: One is through careful use of well-designed coding standards. Large program authors should make key architectural decisions very early on, define a safe, constrained, style – and have the team stick to that style.
In other words: 1. either your C project has a very expensive team of world-class rock stars, or: 2. your software is full of bugs and security holes cut by C' sharp edges. As observed in the mainstream (!) news almost every week.
PS: C programmers shouldn't worry about their retirement; COBOL people can apparently still make a lot of money :-) https://www.npr.org/sections/money/2018/01/10/576879734/e...