3 ms·
Even if it's c++ to c++, the goal of scripting at the end of the day is quick iteration. What is "quick iteration" for scripting will depend on the scriptor. T
by johnnyanmac 2y ago
Even if it's c++ to c++, the goal of scripting at the end of the day is quick iteration. What is "quick iteration" for scripting will depend on the scriptor.
This article is clearly targeted at engineers rolling their own engine, so that audience may find it beneficial keep everything in one language if they are already comfortable with it. As long as the core engine doesn't need to re-compile every little change, it's a win.
- fwsgonzo 2y agoYeah, I can confirm that the iteration speed is fast. I consider the scripting portion a solved problem right now, having used it so long. Gamedev is so many other things though, and practically every corner of the engine has to have convenience functionality in order to reduce the overall workload. It's rough for gamedevs right now, I feel like.
- johnnyanmac 2y agoIMO the big tools are convinent enough to use. But the rampup time to really understand how the engine ticks is dreadful, because documentation drops off a cliff once you want to do more than animate a few dozen actors in a level (and tbf, sometimes that is indeed enough to ship). The other half of the problem is asset production time. But no game engine is really solving that problem. As you'll discover in that domain, the art community is a lot more protective of their techniques and pipelines than programming. Even more so if looking for game ready asset production. Same issue, different cause.