C’s Biggest Mistake (2009)

Re:C’s Biggest Mistake (2009) by prakis on Saturday September 12, 2020 @09:07PM (#24457332)

It simply impossible for C to finish or vanish. It is one of the most tested and rock solid pillar in programming world. Developers already mastered how to handle the issues you mentioned in article. They are not such big to discard C.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by WalterBright on Saturday September 12, 2020 @10:15PM (#24457629)

I mean it in the sense of starting new development of a major new project with it. Of course, C will be around a very long time, like COBOL and FORTRAN.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by sangnoir on Sunday September 13, 2020 @03:15AM (#24459043)

How many new embedded projects are picking non-C languages currently? I'm no fan, but C is a long way from dead.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by zucker42 on Sunday September 13, 2020 @03:25AM (#24459086)

I would wager the percentage of embedded projects than are picking C has decreased in the past 10 years. I have no direct evidence of that, but I think it's a likely guess.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by konjin on Saturday September 12, 2020 @10:01PM (#24457571)

The first thing you do to see if a new processor has bugs is to port a forth interpreter for it.

The first thing you do to see if a new processor is ready for prime time is to port a c compiler for it.

The people who talk about rust replacing c are the type of people who thing that GTK is a reasonable C project.

[ Parent | on HN ]