3 ms·
"If you're just making a game" …for Microsoft's platforms. This article[1] tend to prove that the extra time you spend with OpenGL can be a worthy investment,
by loup-vaillant 17y ago
"If you're just making a game"
…for Microsoft's platforms. This article[1] tend to prove that the extra time you spend with OpenGL can be a worthy investment, even if you are "just making a game". (I know you didn't say otherwise, but you sounded like you thought otherwise.)
[1]: http://blog.wolfire.com/2008/12/why-you-should-support-mac-os-x-and-linux/ http://blog.wolfire.com/2008/12/why-you-should-support-mac-o...
- daeken 17y agoNo, I certainly agree that cross-platform compatibility is important (the D3D10 implementation I mentioned in my post was for WinXP, OS X, and Linux, and spawned from a reimplementation of Win32 on OS X/Linux), but this has to be weighed against the costs. Going with OpenGL, SDL, OpenAL, etc is certainly not the easy route, even with the huge benefits, and for small dev houses it can easily become overwhelming. If your code needs to be cross platform, then OpenGL (or both, but that again is more expensive) is the only way to go. If cross-platform compatibility would simply be icing on the cake, then you need to weigh the development costs of both approaches.
- nihilocrat 17y agoIf you're just making games, you should just use one of the many free, cross-platform rendering engines (OGRE3D, Irrlicht, etc.) or a comprehensive game-maker (Unity or UDK). Both of these options abstract away OpenGL, Direct3D, shader implementations, extensions, etc. I have wasted a pretty huge amount of my life writing engine code when I don't much care for engine problems and know someone else will be able to write something that performs better and has a good-enough API.