When comparing Loom SDK vs FlatRedBall, the Slant community recommends FlatRedBall for most people. In the question“What are the best 2D game engines?” FlatRedBall is ranked 48th while Loom SDK is ranked 49th. The most important reason people chose FlatRedBall is:
Just check the commit frequency on github :) https://github.com/vchelaru/FlatRedBall/commits/master Plus Victor takes community input seriously and is known to shift around priorities based on the pressing needs of the community
Ranked in these QuestionsQuestion Ranking
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.
Pro Continually improving and open source
Just check the commit frequency on github :)
Plus Victor takes community input seriously and is known to shift around priorities based on the pressing needs of the community
Pro Very easy to use
Simplifies routine tasks such as adding entities and files to the game, or tuning parameters, via the FRB Editor called Glue
Pro Great community
Very active chat on gitter: https://gitter.im/vchelaru/FlatRedBall
Victor (the creator of the engine) is available throughout the day to answer questions and solve any problems that may arise, along with the rest of the community members who are ready to assist in any way they can.
Pro Extensive documentation
Very good documentation not only regarding the API details, but also lots of tutorials covering different aspects of using FRB, either on the code-side or on using any of its tools.
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.
Con The editor's UI looks dated
Although functional, doesn't look as flashy as Unity for example, which may put some people off.