When comparing Angel2D vs Wave, the Slant community recommends Wave for most people. In the question“What are the best 2D game engines?” Wave is ranked 36th while Angel2D is ranked 80th. 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 Great for prototyping
The framework is focused on prototyping. It has plenty of features to speed up development. It has a console with a lua interpreter, tuning variables and function calls. GWEN is well supported. Provides a simple interface for Box2D. A simple messaging system with which entities can subscribe to to receive messsages among other things.
Pro Permissive licence and easy to extend
Angel2D is built with the idea that you the game developer should have control over the framework and be able to add features if you like. So the code is BSD-licenced and very easy to extend for anyone that has completed a basic C++ course or equivalent.
Pro Great performance
While Angel2D isn't the best performing framework out there it's certainly no slog when compared to competition. Simply by the virtue of being native it puts itself ahead of engines like Gamemaker and frameworks like Love2D.
Pro Simple interface to lua scripting
If you're not comfortable with a basic subset of C++ it is not recommended to use this framework. But the Lua scripting platform is very nice for generating actors.
Pro Very helpful and simple project set up for newcomers
Often with game engines they throw you into unfamiliar territory and let you explore for yourself. While this wouldn't be a big issue with Angel2D due to it being a very simple framework it kickstarts your game prototyping.
Pro Focused on providing convenient features
Angel was created with game jams in mind, so it's focused on providing as many convenient features as possible, but in a quickly understandable way.
Pro Cross platform
Angel can create games for Windows, the Mac, most flavors of Linux, and iOS. It uses the native build systems on each platform (Visual Studio, Xcode, Make), so you can be up and running as soon as possible.
Pro Low-level code is easily accessible
Low-level code that Angel wraps is always just an easy click away, ready to be overridden or improved.
Pro Very light wrapping on all of the libraries
A very important point that's often underestimated. This framework is designed to be removed. It's not there to provide a complete engine for you which you will have trouble moving away from. The basic interface to Box2D is very spartan. You're given the simplest of Box2D shapes, not even polygonal fixtures. This limitation (seems to be) there so that the integration with the engine is very low. You never create a physics actor with anything more complicated than an enum describing if it's supposed to be a sphere shape or box shape.
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 No asset pipeline
Unlike XNA/Monogame, Gamemaker or many other similar platforms, Angel2D doesn't have an asset pipeline. The extents of the asset importing is manually loading individual files in code or naming them according to a convention to load a set of them.
Con No longer supported
Hasn't been updated in 2 years.
Con Incomplete documentation
The entire framework is technically documented at http://docs.angel2d.com/ but certain functionality isn't described in there but rather it's just a list of functions. They all have descriptive names and it should be common to run into a feature which isn't given example to in the "Introgame"-project example.
Con Abandoned by developers
Sadly this project has been abandoned by the developer. The main github doesn't see any pull requests fulfilled anymore. There's a debugline draw fix on the github that's rather simple to fix. It is recommended you pull that fork rather than the master branch. Though the simplicity of the framework still makes it a good choice for prototyping.
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.