When comparing Flixel vs Loom SDK, the Slant community recommends Flixel for most people. In the question“What are the best 2D game engines?” Flixel is ranked 21st while Loom SDK is ranked 45th. The most important reason people chose Flixel is:
Ports are available for Objective C, C# (XNA), HaXe and [Monkey X](https://github.com/devolonter/flixel-monkey).
Ranked in these QuestionsQuestion Ranking
Pro Many ports available
Ports are available for Objective C, C# (XNA), HaXe and Monkey X.
Pro Built-in pathfinding and following
Pathfinding just means figuring out how to (or if you can) get from A to B. FlxTilemap has a function FlxTilemap.findPath() which returns a FlxPath object, which is just a collection of "nodes", or FlxPoint objects.
Pro Camera system for split screen
Create effects like "split screen" views, or "picture in picture" style displays, or even mini-maps with FlxCamera. Each camera is an independent display object, with its own zoom, color tint, rotation, and scaling values.
Pro Record and play back replays
Replays are essentially a list of what keyboard keys were pressed, and what mouse inputs were given, during a specific time frame. Because Flixel is largely deterministic, you can use that information to recreate a gameplay session that someone else recorded, as long as you have the same SWF.
Pro Basic features provide a solid foundation
- Display thousands of moving objects
- Basic collisions between objects
- Group objects together for simplicity
- Easily generate and emit particles
- Create game levels using tilemaps
- Text display, save games, scrolling
- Mouse & keyboard input
- Math & color utilities
Pro Flixel Power Tools extend the functionality
Flixel Power Tools provide a set of classes and APIs that provide more functionality.
Pro Used to create Canabalt, game that started endless runner genre
Pro Live reload of code and assets across multiple platforms
Loom can live update changes in realtime, allowing you to see them on multiple devices immediately.
Pro Powerful command line workflow
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.
Pro Open source
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.
Pro Familiar and powerful scripting
Pro Good support
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.
Con It is now obsolete
With Adobe Flash dead, Flixel is now unworkable.
Con Development has stopped
Seems like development for Flixel has stopped. The last commit on all of the branches of it's Github repository are from 2011.
Con Poor performance on mobile
Con Documentation is lacking
Con No visual tools support
There's no level editor, asset viewer or any other visual tools in Loom SDK. Everything has to go through command line. I think it's fine if you really like typing.