Yes, you can use C++ to do amazing things. In large-scale projects, that usually backfires, though, unless you contain the "magic", because interactions in C++ are harder to predict.
The problem with C++ is not that you have to know what you are doing - you also have to know what everybody else is doing.
And the "small sacrifice" of a bigger text segment is a big one in this particular domain. We only have 512M available, and a tremendous chunk of that is eaten up by graphics. An executable seriously exceeding ~20MB would spell trouble.
And I'd argue that AAA games are slightly more complex than a fart app ;)
When I code in a team, we don't just write one big mass of C++ and hope that all the interactions work out okay!
Instead, we follow modular programming practices. If some interactions are too slow, we know who didn't optimize his section and we kick the problem back to him.
That would be nice. Except that - again, for performance reasons - we often have to break the boundaries between modules. Most game engines are a tangled web, since many parts are talking to many other parts. (I think there are ways around that, and there will certainly be a post on it. But that's the way things work right now)
So it's not always that easy to just find a guilty party and blame them.
The problem with C++ is not that you have to know what you are doing - you also have to know what everybody else is doing.
And the "small sacrifice" of a bigger text segment is a big one in this particular domain. We only have 512M available, and a tremendous chunk of that is eaten up by graphics. An executable seriously exceeding ~20MB would spell trouble.
And I'd argue that AAA games are slightly more complex than a fart app ;)