Fallacies of Doom - Lessons learned from porting Doom 3 to Java by Mahmoud Abdelghany

So everybody knows the Doom games, right? Every new installment brought brand new ideas, and groundbreaking graphics. But more importantly, they brought the source code of the prior installment to the eye of the public.
Naturally people have played and hacked the code to oblivion, as much as they played the games themselves. And I have the honor to be one of those people.
I (naively) endeavored to port the Doom 3 C++ code to our fantabulous Java. In doing so, I hoped to learn, among other things, more about 3D graphics. …what I didn’t expect though, was for djoom3(cool name huh!) to teach me more about Java!?
Aside from the basic game development intro, this talk focuses on the following: - Some areas where Java should learn from it’s nemesis, C++ - Other areas where the student(Java) becomes the master(C++) - And some promises that were made, but never kept

[uybabayun]

“It’s a horror game, this way it’s much more scary”
I salute you sir 😃

[thecatishere.]

nice lecture, tho its not macro's fault that you cant use them properly. Everyone knows that macro is not a function and its just literal replacement of code and expecting something else (such as SQUARE(x++) is stupid)