When comparing Cocos2d-x and Cocos2d Family vs Allegro, the Slant community recommends Cocos2d-x and Cocos2d Family for most people. In the question“What are the best 2D game engines?” Cocos2d-x and Cocos2d Family is ranked 4th while Allegro is ranked 8th. The most important reason people chose Cocos2d-x and Cocos2d Family is:
25% of iPhone games are made using Cocos2d-x (A Cocos2d mobile variant.) This means you will not be alone in development, and will have access to a large community. You'll know you are developing for an engine that works.
Ranked in these QuestionsQuestion Ranking
Pro A proven engine for mobile development
25% of iPhone games are made using Cocos2d-x (A Cocos2d mobile variant.)
This means you will not be alone in development, and will have access to a large community. You'll know you are developing for an engine that works.
Pro Great script language support
Especially with Cocos2d-JS you can develop games cross web and native, and the native solution have great performance with JS Bindings, much better than hybrid solution.
Pro Supports 3D models with skeleton animation
A new feature since Cocos2d-x v3.1 is support for 3D models (in your 2D game), not only this but support for skeleton animations is included too! This awesome feature allows for impressive characters in your game along with easier, more fluid and realistic animations.
Cocos2d-x is not only open source but also supported by Chukong Technologies of China and USA.
Regularly updated and adding support for the latest technologies. 2014 has already seen the release of Version 3, a new Cocos Studio development toolkit (optional) and support for new technologies like skeleton animation systems Spine and Adobe DragonBone.
Pro Allows for easy debugging
It has a built-in Python interpreter that allows for easy debugging.
Pro Great video tutorials
Hundreds of video tutorials available.
Pro Greater performance than high level APIs
Cocos2d-x is C++ based engine and it has CPU advantages for most platforms because of that. It uses polygonal mesh methods for sprite rendering for using GPU advantages. (You also use quad methods for benefit CPU).
Pro OpenGL hardware acceleration
Pro Easy integration of 3rd party plugins
For example, if you want to add a rating plugin, you use
sdkbox::PluginReview::init(); and if you want to add the Vundle Ad Network SDK, you use the one packaged in SDKBox
Pro Highly active community for questions and support
Cocos2d-x forums are active.
Pro No external dependencies
Because it is based on Pyglet.
Pro Good engine architecture
Allegro is well designed, easy to use and has many useful features.
Pro Good documentation and lots of tutorials
Since it has been in development since mid-90s with hundreds of people contributing to both the engine and documentation, it has all of its bases covered when it comes to standard support.
Pro Per-platform library optimization
Allegro uses DirectX for Windows, and OpenGL for other targets.
Pro Supports desktop and mobile
Support for Windows, Mac OS X, Linux, iPhone, and Android
Pro Freedom to implement your own game engine
You are not bound to the limits of existing game engines, and you can actually implement your own engine.
Con Poor documentation
Most existing documentation is out of date. API documentation sometimes exists, though is usually just a one-liner and more often than not is completely absent. New features and significant system rewrites often make it to a major release without a single line of documentation accompanying them. Cocos2d-x family is developed by Chinese mostly, so market outside of China is not their main priority. Some tools (like Cocos Studio) have China-specific services and markets.
Con Cocos2d-html5 is way behind Cocos2d-x
While Cocos2d-html5 tries to mimic it's Cocos2d-x sister and has the same people working on it, it has lots of restrictions compared to Cocos2d-x: no Spine mesh support, no 3D models, bad text label quality, etc.
Con Poor support and non-existent community
Up until 2013, this was one of the best engines around. However, since then it was bought by a Chinese company and began stagnating - it's virtually in a slow death. Most developers abandoned Cocos in favor of more modern solutions leaving the community weak and the forums with little or no traffic. Although the Cocos2d-x Forum seems to have a decent community going.
Con Can seem very complex for a novice developer
There isn't much documentation or tutorials.
Con Fragmentation; hard to find useful tutorials
Cocos2d family includes different projects: cocos2d-x, cocos2d-html5, cocos2d-objc, cocos2d-XNA. Most tutorials describe techniques specific to single project of the family, and cannot be applied to other projects.
Con Modest functionality
Almost all free alternatives are more convenient, faster, and more functional.
Con Learning curve for hobbyist developers
Hobbyist developers coding alone may experience a learning curve with Allegro of about 200 hours (if you are rusty on C++). To learn quickly, see Mike Geig's tutorials at Fix By Proximity. This learning curve may be fine if you are considering going professional, but are still unsure.
For hobbyist developers not planning on going professional, you may want to look into a complete 2D game engine, rather than a coding library. For example, there are "non-coding" engines that provide support for coded plugins or scripting. But, if you are a dedicated hobbyist planning to use Allegro as your coding library of choice, you can still develop great games as a hobbyist.
Con Isn't great for C++
If you are a fan of object oriented programming, and want to use this library, then the chances are that you are going to be creating a lot of wrappers for functions in this library.
In short, if you're a C++ person, it could be recommended to check out SFML instead.