When comparing Moai SDK vs Starling, the Slant community recommends Moai SDK for most people. In the question“What are the best 2D game engines?” Moai SDK is ranked 19th while Starling is ranked 74th. The most important reason people chose Moai SDK is:
Because it uses Lua + C++.
Ranked in these QuestionsQuestion Ranking
Because it uses Lua + C++.
Pro Gives you total control
You can use your own custom shaders and extend the language with C++. MOAI doesn't give you everything, instead it gives you the tools you need to develop any game you want.
Pro Full source code is available
So it is extendable with C++
Pro Easy-to-use particle engine
Uses a limited subset of Lua
Pro Uses Lua, with LuaJIT where possible
Pro Is used by many pro developers
Moai SDK is used by popular developers including Double Fine for their mobile game, Middle Manager of Justice, and for their Kickstarter hit, Broken Age(formerly, Double Fine Adventure.) It was also used to create the popular mobile game Bubble Ball 2.
This proves that this engine can be used to make fully-featured and fun games.
Pro API interfaces
Has options for development like Hanappe and Rapanui, providing a different way to interact with the engine.
Pro Helpful community
The Moai SDK Forum is active and users will go to great extents to answer queries, post code snippets, beta test, and even purchase and give feedback on each others' games.
Pro Helpful and detailed documentation
Although the Moai SDK is very advanced and uses complicated features, the documentation wiki thoroughly and clearly explains how to use these features, such as the Moai Cloud(a service that provides web services for your game), and multiple ways to build from source.
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.
Con Not for beginning developers
The Moai SDK has very advanced features which allow it to create powerful games. A drawback from this is that it is not very suitable for beginners.
Con Not necessarily tested or stable
Con Scarce documentation
Since it is a minimalist framework there is not that much documentation, but if you are used to reading API references and source code you are good to go!
Con Development has ceased
The last update was over a year ago. Users should not expect things to still work on future OS versions unless they're ready to fix them yourself.
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.