Outside the Unix world, this three-orders-of-magnitude improvement in
C>hardware performance has been masked to a significant extent by a
C>corresponding drop in software performance.

Another part of the fault must be laid to the failure of OO itself to
C>live up to expectations. We examined this problem in Chapter 4
C>(Modularity), observing the tendency of OO methods to lead to thick glue
C>layers and maintenance problems. Today, inspection of open-source
C>archives (in which choice of language reflects developers' judgements
C>rather than corporate mandates) reveals that C++ usage is still heavily
C>concentrated in GUIs and multimedia toolkits and games (the major
C>success areas for OO design) and little used elsewhere.

IDEs make a lot of sense for single-language programming in a
C>tool-poor environment. If what you're doing is confined to grinding out
C>C or C++ code by hand and the yard, they're quite appropriate. Under
C>Unix, however, your languages and implementation options are a lot more
C>varied. It's common to use multiple code generators, custom
C>configurators, and many other standard and custom tools.