Our bulletin board has had this editorial from eWeek hanging for over 4 years now. Still worth a thought.

We have to get over the bias that there’s something dishonorable about choosing languages that prize safety over pure efficiency. Hardware capacity is growing faster than programmer accuracy. It’s time to require case-by-case justification of C and C++, the tools that grease the floor and let developers run with knives.

Have we reached that point yet? Have Java and .NET taken over, or are C and C++ still ruling the roost? If so, what is the holdup?

3 thoughts on “Flashback: Insecure Languages

  1. Joe Blow says:

    Installed base?

  2. Peter says:

    Installed base can justify it for continuing modifications to an existing app written in C/C++… Not for new development efforts though.

  3. Joe Blow says:

    Installed software library base?

Comments are closed.