Loom SDK vs HaxePunk

Loom can live update changes in realtime, allowing you to see them on multiple devices immediately.

Loom Turbo ($5/mo) gives access to powerful command line tools. For example, "loom new" to make a new project, "loom run" to run it. Packaging, deploy, and live reload are done automatically for you.

The Loom runtime and LoomScript compiler are open source, with code available on GitHub, allowing you to have the freedom to fix the bugs and add the features your game needs.

Loom includes over 30 examples ranging from complete sample games to demos of single features.

Loom's scripting language is immediately familiar if you know JavaScript, ActionScript, TypeScript, C#, or Java. Internally, it uses a proven VM technology with over 10 years of heavy use in games.

Loom devs are helpful.

Loom can deploy to Windows, OS X, Linux, iOS, Android (including Nook, Kindle Fire and Ouya). There are also custom port available for WP8, Blackberry and consoles.

Useful for mobile games and soon consoles (OpenFL has a console port in the works).

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.

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.

This comes with blazing fast compile times, proper static typing, multiple output targets, and a powerful macro system.

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.

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.