When comparing HaxePunk vs Blacksmith 2D, the Slant community recommends HaxePunk for most people. In the question“What are the best 2D game engines?” HaxePunk is ranked 22nd while Blacksmith 2D is ranked 48th. The most important reason people chose HaxePunk is:
Useful for mobile games and soon consoles (OpenFL has a console port in the works).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Joystick and multi-touch support
Useful for mobile games and soon consoles (OpenFL has a console port in the works).

Pro Crossplatform testing/releasing
HaxePunk uses OpenFL which means you can compile to just about every device. A lot of the rendering code has been optimized so if you use HaxePunk’s graphic classes you are pretty much ready to deploy on any target.
Pro Generic entity system
A generic Entity system that only uses what you “attach” to it. If you need collision masks they are available but if an entity doesn’t need to collide with anything then simply don’t add a mask. Same goes for graphics.
Pro Written in Haxe instead of AS3
This comes with blazing fast compile times, proper static typing, multiple output targets, and a powerful macro system.
Pro Multiple collision masks
HaxePunk has added several collision masks beyond what FlashPunk had including a grid with slope values, circles, and polygons. This is in addition to FlashPunk’s tile grid and hitbox.
Pro Tweens
Tweens are available just like they are in FlashPunk. If you need to interpolate values for sounds, movement, etc… it’s probably already available as a tween. There is also a VarTween that lets you interpolate any value you want.
Pro Cache as bitmap
Automatically detects changes and updates bitmap cache. Allows to gain even more performance on heavy scenes and runs smoothly on old devices.
Pro Most valuable when size matters
All engine code is written in ES6, fully GCC typed, allowing to eliminate all dead code from your app.
Pro Advanced scene graph and rendering pipeline
Dirty flag tracks scene changes and avoids unnecessary calculations and context calls. If no changes were made to the scene since last frame, no rendering will be done. Battery efficient.
Pro Good performance
According to the tests on the Github page, the performance is better than in Phaser!
Pro Good and clear source code
The source code is well commented and easy to understand.
Pro Super small build size
Super small build size through dead code elimination. The best for playable ads and Facebook Instant Games.
Cons
Con Messy / fragmented documentation
Not a lot of documentation is available.

Con Small comunity
It’s a small but growing community.
Con Small community
The project is young, so the community is extremely small.
