The thing is though, when you post things as facts (whether you know them to be true or not) and you're flat out wrong, you're going to get criticized.  Next time you feel like posting your thoughts, do some research first or, well, just do research first.  Don't assume you're just right because is shows your ignorance (see how I used it right there?).

 I think he is talking about the OP

 Pst-- he is the op.  :p

 Sorry I mean first post... I need to sleep

Lets just break this apart a little.  I'll start with twesterm:

 "You will make yourseld look a lot less like an complete idiot if you stop pretending you know what you're talking about."

 Okay, admitedly, he's a little harsh here, but he's also giving you some honest advice. the problem isn't so much that you didn't know what you were talking about, but that you didn't bother to verify, nor did you bother mentioning that you haven't personally verified. Usually if you point out ahead of time that you are just guessing, then people will just correct you and move on. You also could have easily avoided this whole issue if you took a few minutes to do a google search "Playstation 2 Xbox Gamecube Developer Difficulties" or something like that to actually verify some of those obvious assumptions you made.

now on to your stuff: 

"first of all dude, chill the hell out before you get me upset!"

Why? What are you going to do? Turn green and bust out of your clothes, reach through the computer and beat him up? As I've pointed out, he really wasn't bashing on you senselessly, he was making an honest point that you could have learned from if you weren't so busy feeling sorry for yourself.

"*the nerve how ignorant some people can be*"

The reason people find this statement so amusing is because you are using ignorant as a synonym for rude, which it isn't. Some people are rube because of ignorance, but ignorance is defined as a lack of knowledge. By describing his behavior as ignorant, you demonstrated your own ignorance of the word ignorant, and this was compounded the fact that you had already demonstrated a certain level of ignorance about the consoles you had been talking about in your original post.

"it was just my thoughts!!!!! i am not an analyst!!!"

 We already know you're not an analyst, but you didn't say anything along the lines of "this is my take" or "this is what i'm guessing could be the cause" The way you stated your case was as if you had a position of authority or knowledge of the issue, which you don't really have. A little humility can go a long way in how your thoughts are received by others.

"if you don't like what i said then leave my thread and make one yourself dammit!!!!!!!!"

 I don't know about the others, but I have done a few analasyst threads already. For the most part, they've been fairly well received. With this in mind, I'm giving you a little advice on how to improve yours and also what mistakes you should be watching out for. You made a few very obvious mistakes in a public forum, you can't expect to not be criticized for that. You can either continue trying to improve and learn from the criticism, so you don't make those mistakes, or you can give up.

The XBox was (relatively) easy to develop for because of how closely it matched a PC in terms of hardware and development tools; the CPU was an Pentium 3/Celeron hybrid running at 733MHz, its GPU was based on the Geforce 3, and most interaction with the graphics hardware was handled with a modified version of DirectX 8. This closeness to the PC is why the XBox received so many (often console 'exclusive') PC ports, why so many western third party developers favoured the XBox, and (potentially) why the XBox performed as well as it did.

After how many developers struggled with the N64, Nintendo focused on producing a system which was much more straight forward, had few bottlenecks and provided excellent real world performance. The Gekko processor was designed by IBM using their G3 core (the same basic core at the heart of the XBox 360, PS3 and Wii) with an extended instruction set; the Flipper GPU was designed by a small hardware company founded by former silicon graphics engineers who were devloping flight simulators named ArtX. Overall the few third party developers who really focused on the Gamecube (Factor 5, Capcom) achieved some amazing things, but most third parties did rushed ports of PS2 games and never took advantage of the Gamecube's capabilities.

The PS2 was a disaster in terms of ease of development and many initial PS2 games looked worse than Dreamcast games; third parties started to achieve amazing things on the PS2 mainly because its sales ensured that it would be the target platform for (pretty much) every game, the extra money needed to optimize code (or licence highly optimized middleware) was justified under the assumption that improved graphics would increase sales of the game.

As a guess, the PS3 is facing so many delays this generation because managing a project as large as PS3 games are becomming is not a simple task. In most software development (or any engineering project) a team of over 10 or 15 people is seen as very large and you need a highly experienced person in charge; many of these PS3 games now have teams in excess of 100 people and timelines of 3 years, like all projects unmanaged risk could delay these games by 50% to 100% of the initial timeline.

@HappySquirrel: Don't you hate it when you kill a thread by making sense?

Didn't the N64 version of RE2 have in-engine FMVs while the ps1 version had CGI FMVs?

Developers actually tend to use middleware on all the new consoles - it's the middleware developers who wear-hide most of the complexity , the Main cost of games development is probably in Graphics artists and designers, level editors , sound artists , actors , motion capture and producers rather than low level programmers who i belive constitute only a small proportion of the cost of developing a game now days. It's easier than ever for developers to get performance and compatibility from the 3 new consoles they all run PowerPC of some sort with vertex/pixel engine ,and have middleware.

This IMO had actually caused problems that there are few real programmers in gaming anymore because the (Wii/Ps3) Motion sensing inputs are not supported by the current middleware properly and the users of the engines are clueless about how to use the sensors - In other fields ie avionics they have specialists who deal exclusivly with motion , sonar , sensors while the games industry people have trouble understanding anything more complex than a joystickand it shows badly in some cases.

The other areas it shows in are the lack of new ideas in games in general they cant go outside the envelop of the middleware engines leading to many of them being same game play different bad guys -
how many games are there where the centeral play is that person walks around and simply shoots stuff probably 90% , and the only other intereactions seem to be scripted cutseens or the usual i have found a key now so i can open then next door.
Still things will improve gradually i hope .

Wow. I totally understood that. Yes. The Ps3 is hard to program for