Comment Re:The present and the future (Score 1) 576
I've seen this argument pop up time and time again, and it has come to the point where it induces nausea!
There is no doubt that Microsoft is a monopoly. But unless I am mistaken, all of those here have chosen to develop applications for personal computer class machines knowing full well what kind of tyrannical power MS wields.
But you have to ask yourself one question as a game developer. What are you trying to develop? When a user runs a well developed game, do they give a rats ass if the rasterization code calls glDrawElements() or g_D3DDevice->DrawPrimative()? No! They see the interaction of objects in a universe created by the developer. They experience the rules of physics or psuedo-physics that go into play upon their interaction with the game engine. What will make a good game has NOTHING to do with the graphics API in use.
Concentrate on GAME programming. Graphics APIs are interchangable; good game play is priceless! If you can use your graphics API of choice, be proud of your accomplishments.
I've suffered the same wracking back and foward between API's myself, forgetting what was important. I've decided to develop my rasterizer as seperate from my game engine as possible! This way I can replace the graphics API any time I want without changing anything having to do with game logic.
If you make a crappy game you can not blame it on the graphics API. A crappy game is a crappy game no matter what it looks like. Making a top selling game is a matter of playing the capitilistic game and simply going with the flow no matter how polluted the water is. Money is the devil's special blend of poison. If this is what you want from developing games, so be it!
Daniel Piron
There is no doubt that Microsoft is a monopoly. But unless I am mistaken, all of those here have chosen to develop applications for personal computer class machines knowing full well what kind of tyrannical power MS wields.
But you have to ask yourself one question as a game developer. What are you trying to develop? When a user runs a well developed game, do they give a rats ass if the rasterization code calls glDrawElements() or g_D3DDevice->DrawPrimative()? No! They see the interaction of objects in a universe created by the developer. They experience the rules of physics or psuedo-physics that go into play upon their interaction with the game engine. What will make a good game has NOTHING to do with the graphics API in use.
Concentrate on GAME programming. Graphics APIs are interchangable; good game play is priceless! If you can use your graphics API of choice, be proud of your accomplishments.
I've suffered the same wracking back and foward between API's myself, forgetting what was important. I've decided to develop my rasterizer as seperate from my game engine as possible! This way I can replace the graphics API any time I want without changing anything having to do with game logic.
If you make a crappy game you can not blame it on the graphics API. A crappy game is a crappy game no matter what it looks like. Making a top selling game is a matter of playing the capitilistic game and simply going with the flow no matter how polluted the water is. Money is the devil's special blend of poison. If this is what you want from developing games, so be it!
Daniel Piron
