I’m developing a mobile app that we’re hoping to roll out in a few months and support it for many years from now on (hopefully!). The project started a few years ago, then we had a long break for other, smaller projects, and now we came back to it, already having a big codebase in cpp / Cocos2dx. Now, CocosCreator has come a long way in the meantime and I’m sort of starting to worry that writing in cpp becomes inefficient compared to using CC, and a bit… well… obsolete style?
I was hoping to write all new stuff (e.g. new scenes) in CocosCreator and add it to my existing project - as a very slow and never-100%-migration - however, judging by what I’ve read, and this topic Integration of Cocos Creator v2.1.0 with cocos2d-x 3.17(c++) , it’s become impossible. Is that really so?
I guess that it should be reasonably safe to stick to cpp, since CocosCreator will always rely on cocos2dx, right? Do I have anything to worry about, if I am planning to keep the project in cocos2dx? It should always be manageable to develop more or less anything I need in cpp, right?
Edit: @slackmoehrle , if you could spare a few minutes, I would be grateful.