4 ms·
I disagree with his advice on not using game engines. Just about any finished game will rely on someone else's libraries or code at some point. It would be insa
by reedlaw 16y ago
I disagree with his advice on not using game engines. Just about any finished game will rely on someone else's libraries or code at some point. It would be insane to duplicate all this effort from scratch, except maybe as a learning exercise. Ogre3D is a good engine for C++ and Unity 3D can even use javascript. I learn a lot about actual game construction and design while using these engines, while efforts at reinventing the wheel usually end in frustration.
- sp4rki 16y agoI think his point is to not focus on an engine. You don't work for a studio and are just starting out, you need to get the experience and knowledge first. Sure when you're working in Starcraft 3 or Quake43262 you'll be using an engine made by someone else, but the fact that you now know how that engine works on the inside because you didn't use them when you started makes you invaluable. It's the same deal with Ruby programmers and only Rails programmers we have now.
- PilotPirx 16y agoEspecially true for beginners who for a long time wont be able to write that kind of code anyway. Python + Panda3D on the other hand allows even a beginner to get a few simple models on the screen within short time. And that kind of motivation you can get out of it will pay for itself, even if you plan to add C++ in the future.