Linked by Thom Holwerda on Fri 15th Feb 2013 10:40 UTC
General Development "Since I left my job at Amazon I have spent a lot of time reading great source code. Having exhausted the insanely good idSoftware pool, the next thing to read was one of the greatest game of all time: Duke Nukem 3D and the engine powering it named 'Build'. It turned out to be a difficult experience: The engine delivered great value and ranked high in terms of speed, stability and memory consumption but my enthousiasm met a source code controversial in terms of organization, best practices and comments/documentation. This reading session taught me a lot about code legacy and what helps a software live long." Hail to the king, baby.
Permalink for comment 552694
To read all comments associated with this story, please click here.
RE[7]: Code Review
by Alfman on Fri 15th Feb 2013 22:36 UTC in reply to "RE[6]: Code Review"
Member since:

It sure is complex, but humans can still have the upper hand in some of the cases you've mentioned. Compilers are often given more credit than they actually deserve. We treat them as though they're god like, but in reality they can be pretty dumb sometimes.

I think compilers will have to gain more artificial intelligence before they can persistently match & beat the best hand optimizations. I believe this will happen, but it just hasn't happened yet.

Edit: By my criteria, this will have happened once a compiler can consistently generate code listings which no human is able to optimize any further for the given target.

Edited 2013-02-15 22:40 UTC

Reply Parent Score: 2