There seems to be a lot of talk about how Linux can't compete with Windows in gaming, so here is a list of the games I have installed on my computer right now.I'm running Debian Etch 2.6.18-3-686 .
I haven't included the stock games that came with my kde/gnome desktops.

Thunder and Lightning
Flightgear
Postal2
Secondlife
Enemy Territory
Bzflag
Criticalmass
Frozen Bubble
Gl-117
Torcs
Trigger
Briquolo
Nexuiz
Open Arena
Tremulous
Adonthell
Planeshift
Balazar
Slune
Boson
Globulation2

Linux just needs to be more "stupid proof". I agree many things are faster but less intiutive.

Linux to me seems more usefull for programming, in this way linux is more intiutive and much easier to use than on windows. On windows using the command line is a little bit more work than on linux.

Also linux is usefull for testing out algorythms, generating test cases.

People that use Linux are mostely computer humans (people good with computers), or (as I see on this forum) being (forced?) by a computer human to use.

If we really want linux to get more support from manufacterurs, (as I think) more standards need to be developed on linux such that it would be possible to distribute executables without needing to distribute any line of code and for the executables to be usuable from any linux computer.

Also the linux executables format need to be updated so icon information may be put into it and a file manager may read it and put a picture of it.

(By the way I'm not good at english thank you)

One reply I may get is that this is turning or mimiking windows. That is true, however doing this will enable manufacterurs to more safely distribute there products.

Another reply might be: This would be open source violation or something similar; Not everyone wants to give their code away but is willing to give compiled functions to be used to make life easier. This is a matter of choice, to chooce to give code or not. However certain aspects of linux should be completely open source such as its kernal and other linux products which are contributed by developers around the world.

I guess your definition of "intuitive" is just very different from mine...

I'm not sure what you meant by that.
Game manufacturers don't need to show any source code at all. It's their software, their license. No need for any additional source code here...
Their's also nothing "standard" about what Microsoft is using (DirectX has more compatibility issues than anything else).
A bigger user base might help here...

Both RPMs and DEPs already do this (same thing for about all other less known linux binary formats). If an installer from a game manufacturer doesn't do this, that's their choice and fault.

You're wrong. Commercial game developers can use any license they like. (DOOM3, QUAKE4, NWN,... are all commercial and closed sourced games with a native Linux client)
As for GNU/Linux users, you're a 100% free to use whatever you want in user space. Non of this is covered by any FOSS license (including GPL).
Do read the GPL yourself before making such statements:
http://www.gnu.org/copyleft/gpl.html

sorry I made a fool of myself, I don't know too much about linux. When I look at the executables on linux I alway's see a gear.

I came to this conclusion by haveing to compile code most of the time under linux. I have a question though about this: Lets say I make a game using OpenGL and compile using g++ for i386, how compatable will it be with other computers running linux?

Yes I should read it, Sorry I misenterpreted.

Yes it seems so. I remember when I first started to using linux (comming from windows) when trying to do things my intiution wasn't that much help. However after a while my intuition became more usefull. Just takes some time to adapt.

Personally I think Linux is great for programming and developing

Gaming on Linux is fun but I don't always have time for it. Sauerbraten has awesome graphics, even though it is more of a game engine demo than a real game.

It always takes a little effort to make the transition to a new OS. For example, I was using an very old version of Mac OS on an old Mac Classic (can't remember if it was 1 or 2) but when I got my Windows 98 Compaq Presario, I was completely lost. But I eventually learned different things by pure experience, as well as trial and error.

On Linux, sometimes I figure out things on my own as well. It seems, according to Google, that most problems that I encounter are mine only, and no one else has experienced them or posted them on the net. But usually the problem is caused by not reading the README or INSTALL files, or whatever.