When comparing Codea vs Wave, the Slant community recommends Wave for most people. In the question“What are the best 2D game engines?” Wave is ranked 35th while Codea is ranked 100th. The most important reason people chose Wave is:
In addition to online [API documentation](http://waveengine.net/Engine/Documentation), the Wave Engine team provides [tutorials](http://www.indiedb.com/engines/wave-engine/tutorials) via IndieDB, plus [sample projects](https://github.com/WaveEngine/Samples) and "[QuickStarters](https://github.com/WaveEngine/QuickStarters)" via GitHub.
Ranked in these QuestionsQuestion Ranking
Pro Helpful code editor
Errors show up live, as you type. Smarter autocompletion picks up your local and global variables, including nested types. Everything else is just plain smarter, from indentation to highlighting.
Pro Ships with music and sound packs
Codea ships with three great music and sound packs, composed just for Codea and free for you to use in whatever you create.
Pro You can code on an iPad and easily distribute the game
Pro Location library
Location library lets you make use of the GPS inside your iPad. Get your latitude, longitude, altitude and more with a dead-simple API designed specifically for Codea.
Pro Supports coding in C#, F# and Visual Basic
Wave Engine explicitly supports all three core .Net Platform languages.
Pro Oculus Rift support
The Wave Engine team provides an official, open-source Oculus Rift extension via GitHub.
Con Not many tutorials available
Con Mandatory splash screen
Games and applications made with Wave Engine must display a splash screen advertising it. No splash-free license option is available.
Con Outdated UI
The UI looks like it is from Windows XP days. A refresh is much needed.