"Game developers" are morons

Why are 80% of people on Gamedev.net or GAYM DEVELOPERZ in general complete idiots?

LOL I USE DIRECTX 2 MAEK GAYM HURRRR HURRRR

Because smart people would be doing something more interesting than game design.

1. Playing games are fun.

2. Many people think that because games are fun, everything about games is fun.

3. Games have a myth about them, same as "working for google".

=> Many people want to go into games. Including all the idiots. And the Idiot ratio is higher, because the smart one realize that:

Programing games is not more fun than writing a banking application. What makes the difference is the workplace, but working for a game will not guarantee you that...

Kids gravitate to games, that's why.

The people who actually do it for a living often have difficult problems to solve, and solutions to those are often found in thick books or academic papers.

If you're not looking at those, you really won't need help from a forum full of children with grandiose ideas anyway.

>>3
>>4
ITT bitter people who wish they knew how to write games

Writing games is simple. The point is not skills, but the time it takes to make a decent game. (Or the effort and money to assemble a team of devs.)

>>5
LOL, "know how to write games". Everyone knows how, there's nothing arcane about game development.

Oh, dear god no! I only started writing games when I was a preteen! Wow, so very fucking incredibly amazingly hard! I must be Newton or something.

Developing some kinds of games can be quite difficult, but you're not going to find help from gamedev. You might by hiring someone with a postgrad degree in physics and numerical computation though.

The first real program I ever wrote was a 2D fighting game featuring stick figures. That was in 1994, I think.

>> 8
No you don't.

You must differentiate between engine development and game development. Two pair of shoes.

But event the most difficult things, such as AI, Compiler/Interpreter or Physics-Kernel is not that difficult. The point is that you do not have to invent anything, it is all there, because all game (and engine) development are outlined by academia  at least five years in advance.

Writing software is NOT difficult. Figuring out the mathematical, physical and / or numeric is the real difficult thing. But games do not have to do that...

You must differentiate between engine development and game development.
Ah, okay. That's a good argument, although I'm tempted to ask the inevitable "eat your own dogfood" question regarding engine developers.

Figuring out the mathematical, physical and / or numeric is the real difficult thing. But games do not have to do that...
It appears to me that they're increasingly going hand-in-hand. I was recently watching this: http://channel9.msdn.com/Showpost.aspx?postid=314874

While he's not writing a game, he's employed and working explicitly to develop some of the algorithms that'll be used in a game. I'm not sure what that should be classified as.

>>10
Wrong, fucktard. Writing software is easy IN THEORY, but hard IN PRACTICE.

It's like, it's not that C is a difficult language -- writing large programs in C is what's difficult. All the stuff around it. Not to mention project management and planning.

>Physics-Kernel

hypocrisy, etc

>>1 Game Developers are not complete idiots in general, you just had some bad experiences unrepresentative of the average game developer (Andre LaMothe?). A lot of kids are drawn towards gamedev.net, but among the users are some pretty clever people, see Oluseyi, Fruny, Yann L.

Nothing is wrong with DirectX, it's pretty mature, up to date, has a lot of features and is good at what it does. I'm guessing that you don't like it because you can't use it on your favorite OS, which approx. 12 other people use.

For some non-idiot game developers see:
Peter Molyneux
Tim Sweeney
Richard Garriott

p.s. Only kidding about Andre LaMothe, he is really cool. Handsome too.

ITT people who wish they could write games bash people who can.

ITT people who state that people who wish they could write games bash people who can have never written a game

>>17
>>18
ITT PEOPLE COPYING ME

>>16
Handsome too.
Do I hear wedding bells?

Tim Sweeney
Jill of the Jungle was the only good game he made

>>21
Jill of the Jungle was not a good game.

Anonymous
Jill of the Jungle was the only good game he made

>>23
Jill of the Jungle was not a good game.

What about Xargon? That was fun.

Xargon was not a good game.

solar winds

>>27
Only the first part was good. It was all downhill after the shareware.

Here is why game coding is win:

1. You get to write tight code with interesting algorithms as opposed to Enterprise Java Beans Web 2.0 shit

2. Console coding means that every machine that your code runs on is identical. Hence you don't have to write nearly as much portability scaffolding or abstraction layers, and you end up with much prettier code (although this is usually nullified by all the inline ASM shit everywhere)

3. Comparatively much less maintainance than business applications; again, there's way too much 70s shit written in COBOL still kicking around that is being actively maintained.

4. You get to summon a massive world into existence inside your machine that you can interact with in interesting and semi-meaningful ways. And I mean that's just cool. Get a good procedural generation system going and you can even turn a 32 bit number into a planet.

You know, I've concluded that almost everything is awesome, since it's not Enterprise Java Beans Web 2.0 shit, which is like 75% of the open jobs at the moment.

If you're in anything other than enterprisey java, you're a fucking genius. Even the PHP monkey down the hall, cuz he's having fun (somehow).

>>30

I was somewhat happy doing PHP (merely for the excessive pay I got). But then again, I nearly killed myself a month later and quit.

Well, okay, I'll admit I had no fun working with Zope either. But that only proved to me that I'd have even less no fun with Java, because Zope is like... J2EE for Python.

lol wut