The Shrine

http://gamearchitect.net/Other/archive.html

I found it because someone linked to his brief essay Why C++?. (Regarding that essay, I think he underestimates the power of closures and functional programming general, but the new C++ standard is getting closures. But it'll probably be years before it's in all compilers.)

Bookmarked! I will take a look, thank you.

I've already switched to C# probably forever, though. There are many, many good reasons that C++ dominates the industry, but I just can't do it as an indie anymore when C# offers so many advantages in terms of cutting down dev time.

I printed a copy to read at lunch. Looks interesting.

I ask a different question: Why Java? For some strange reason, it seems like Java is the language of choice for just about any in-house development, and Java programmers are too numerous to count. Unless you're designing something to be cross-compatible with multiple OSs in a JVM, there is simply no point in using the language.

Perl is more robust. PHP is faster for the web. C/C++ is faster outside the web. The language was designed as a compatibility language, but too often, it's used as a catch-all for any project.

Cross-platform compatibility was one of Java's goals, but it actually has nothing to do with the language itself. The Java language didn't need to compile down to bytecode and using a VM.