Live data from Hacker News

Doom3 is the proof that “keep it simple” works

gamedev.net

41–50 of 111 posts

Re: Doom3 is the proof that “keep it simple” works

#41
> Note: Please offer only positive, constructive comments - we are looking to promote a positive atmosphere where collaboration is valued above all else.

And keep your rose-colored glasses on at all times. You shall see no evil, hear no evil, speak no evil and never grow out of childhood.

Re: Doom3 is the proof that “keep it simple” works

#42

Fabian Sanglard's exploration[1] of Doom3 is much more in depth than this article, though the author does quote Sanglard's analysis albeit with a small source link [1] http://fabiensanglard.net/doom3_bfg/index.php

For what it's worth, that code review is for Doom 3 BFG. This is the review of vanilla Doom 3:

http://fabiensanglard.net/doom3/index.php

The vanilla code review goes into the app structure first, and (what little I've read of) the BFG review compares that codebase against the vanilla one.

Re: Doom3 is the proof that “keep it simple” works

#43
post #35

No one have issues with source code files 5100 lines long? https://github.com/dhewm/dhewm3/blob/master/neo/game/ai/AI.c...

You make it sound like it is a single 5100 line long method. It seems actually very well organised in that file.

If you're using any kind of IDE then this wouldn't bug you as you can just jump to the point in the file you need.

Re: Doom3 is the proof that “keep it simple” works

#44
post #37

> The game was a commercial success for id Software; with more than 3.5 million copies of the game were sold. Wrong/Cheated. It was such a success that they had to sell the company - they sold ID-Software...

Why are you referring to the process of selling the company as an opposite of financial success?

Re: Doom3 is the proof that “keep it simple” works

#45
post #19

Earlier quoted context omitted.

I was seated at the restroom at work yesterday morning when I noticed a strip of plastic had been added to the gap between the metal stall and the metal stall door. It was branded Privacy Cover (patent pending). Welcome to the future where everything is branded and everyone is an Avon lady, endorsing some set of pet products :) [a] http://www.rbahelp.com/toilet-partition-privacy-strip-instal... [b] http://www.partiti…

I didn't realize people peeking through the slim slit was an issue.

In Chinese public bathrooms, it's even less of an issue

Re: Doom3 is the proof that “keep it simple” works

#46
post #19

Earlier quoted context omitted.

I was seated at the restroom at work yesterday morning when I noticed a strip of plastic had been added to the gap between the metal stall and the metal stall door. It was branded Privacy Cover (patent pending). Welcome to the future where everything is branded and everyone is an Avon lady, endorsing some set of pet products :) [a] http://www.rbahelp.com/toilet-partition-privacy-strip-instal... [b] http://www.partiti…

I didn't realize people peeking through the slim slit was an issue.

I've been to America - on some stalls that gap is not what I would call slim.

Re: Doom3 is the proof that “keep it simple” works

#47
post #37

> The game was a commercial success for id Software; with more than 3.5 million copies of the game were sold. Wrong/Cheated. It was such a success that they had to sell the company - they sold ID-Software...

Doom 3 - 2004

ZeniMax - 2009

It seemed to do well enough to slow the need to sale for five years or so.

Or maybe, just maybe, it was so successful of a company that another company bought it to share in the success.

Re: Doom3 is the proof that “keep it simple” works

#48
post #26

https://github.com/dhewm/dhewm3/blob/master/neo/game/Target.... This is the "nicest looking code [you] have ever seen" ?

What's wrong with this?

Over 150 lines of code in a simple method?

C-style declaration of all the variables in the beginning? (Yes, I know what Carmack said about how he written the project; this explains it, but doesn't make it good C++ code.)

Unclear flow with just one comment, which doesn't really explain anything?

Re: Doom3 is the proof that “keep it simple” works

#49
post #6
post #4

Not to brag but https://github.com/dhewm/dhewm3/blob/master/neo/idlib/Heap.c... (from line 154 down) that seems like another point against using tabs.

I always heard "Tabs for indenting, spaces for aligning."

That works but takes a lot of discipline. More than any team I ever worked with had.

Re: Doom3 is the proof that “keep it simple” works

#50

Earlier quoted context omitted.

What's wrong with this?

Over 150 lines of code in a simple method? C-style declaration of all the variables in the beginning? (Yes, I know what Carmack said about how he written the project; this explains it, but doesn't make it good C++ code.) Unclear flow with just one comment, which doesn't really explain anything?

You should try a Perl codebase. In just this one module I'm looking at, there's methods with 505, 880, and 995 lines.
Post reply on HN