When comparing Starling vs HaxePunk, the Slant community recommends HaxePunk for most people. In the question“What are the best 2D game engines?” HaxePunk is ranked 22nd while Starling is ranked 78th. 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 Lightweight
Starling is just 12k lines of code and doesn't try to do everything — but what it does, as efficient as possible.
Pro Feathers User Interface Components
With Feathers, you can easily add great user interfaces to your games — or even create business apps with Starling.
Pro Free and open source
Starling is available for free with code available on GitHub.
Pro Strong community support
Forum is always active with knowledgeable developers and with lot of inside info, and post mortems.
Pro Works with Flash
With UI, you can design it in Flash Professional (powerful 2D editor), export to swf file, use GAF convert swf file to gaf file, finnally, load gaf file to Starling. GAF can convert a lot of file swf to one atlas. Alway use same resource in design files (fla) to optimize atlas size, avoid duplicate asset in atlas.
You can use flash to create animation for starling.
Pro Hardware accelerated rendering
Let the GPU do the rendering, the CPU has more important tasks to do.
Pro Cross Platform
It can be exported to web flash player, iOS, Android, Windows, and OS X
Pro Works with AIR's native extensions
Using AIR's native extensions any native code that can be written can be run and used by the game engine.
Pro Constantly updated
New features are added regularly.
Pro Better performance than most alternatives
Starling can run more animated display objects than Unity2D and many others frameworks at 60 fps.
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.
Cons
Con Poor text/font support
It supports only 4 features for text rendering:
- bitmap font with batching.
1.1. basic distance fields with support for outline and filters via MeshStyle.
1.2 the new multichannel distance field, the ultimate solution for bitmap font rendering. - Draw and upload texture in runtime
So every new text field required texture uploads or vertex/idnex buffer uploads.
skipUnchanchagedFrames keep the backbuffer static for scenes without changes between frames, leveraging a good rendering optimization.
Con Engine supported mainly by one man
Its open source but in most cases community features or pull request are canceled.
Con Messy / fragmented documentation
Not a lot of documentation is available.

Con Small comunity
It’s a small but growing community.
