ziggurcat wrote...
Lumikki wrote...
ziggurcat wrote...
marshalleck wrote...
lol, John Carmack is neither lazy nor terrible, he's a 3D game guru. If he says developing for PS3 is a pain in the ass, it probably is.
except it isn't.
Are you developing 3D games for PS3?
As general comment:
Sometimes hardware can limit stuff as seeing all the possibilities.
after a little more than 4 years into the PS3's development cycle (more, if you count the time devs would have had access/knowledge of the PS3's architecture prior to its release), the "it's too hard/a pain in the ass to program for the PS3" argument does nothing but demonstrate one's laziness.
you know, as a general comment.
Let's take your logic and use it on a different extreme example to show you a flaw with it.
Let's say, that to write a program that writes "Hello world" on the screen, you would need to write a novels worth of code that depended enirely on what you writing on where on the sceen you wanted to outut it, to do this task. This would, by most people, be considered as being a "Pain in the azz" to code in this way. Fast forward 4 years, and you would still need to write an entire novel based on the parameters of location and text and whatnot. It would still be "A pain in the azz", regardless of wether o not time that the system you write this kind of excessive code for is substantial in how long it have existed.
If writing code for a specific platform is annoying to do so, it doesn't become less annoying just because time passes. To this day I will claim it's a "painin the azz", for example, to write assembler code, despite it having existed as a language for ages. Yet for some hardware platforms/solutions this is exactly what you ned to do. Doesn't make it less annoying.
So as you see by this detour of an xample, just because something have existed for a while, it doesn't mean it becomes less annoying to write code for it.