Yea and too bad that creator developers have no idea what they are doing… as I believe.
It’s because loader code also requires changes of engine code, which is hard to merge or don’t even wanted to be merged…
Yea, thats why I choose(like) to use it instead of just official version. It includes all fixes from original + additional fixes.
As I see, it’s because when he pushed update(some time before he actually created some pull requests time to time) and tried to spent time with it by describing what and why it’s needed - actual result is bureaucracy, and pull was just ignored or like put on backlog or need to be tested and so on… Or even worse - pull closed(ignored) without merge, with some reason. So he probably just don’t want to waste time now, too much other work needs to be done.
I’m developing my game using this branch for about 9 months and never faced some crash or even problem with it, it’s very stable as for me.
What about future… it’s used in production games, so it’s all alive and supported… I hope for a long time.
Actually, when I’m look at cocos creator - I’m sure that it will fail like cocos studio. So what happened next… maybe official cocos2d-x will not be supported then. Or even maybe Swift will be used by google on android and so C++ and js, lua will be like abandoned and not needed. New cross-platform engines will arrive based on just Swift. I don’t know…(Swift code will run on Google’s Fuchsia OS)