When comparing Genome2D vs Wave, the Slant community recommends Wave for most people. In the question“What are the best 2D game engines?” Wave is ranked 33rd while Genome2D is ranked 47th. 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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros

Pro Lightning fast
It's the fastest gpu-based framework out there for flash. It's beautifully optimised. It has very low rendering latency, low level OpenGL calls that other tech simply cannot do (ie Unity) due to Stage3D, and thus can render a lot more data quicker
Pro Cross-platform mobile, desktop and web
Supports Windows, Mac OS X, Linux, iOS, Android, Web and native Flash.
And with the HTML5 export, it also potentially supports development for the Wii U :)
Pro Haxe!
Haxe is a strictly typed programming language that saves development time but still compiles high performance executables, and can build for tons of different platforms (flash, c++, html5, java, c#, etc.)
Pro Access to direct draw features
Has access to direct draw features so you can make you own rendering structures (scene graphs etc).
Pro Automatic dynamic batching
Automatically batch geometries with dynamic batching techniques (by using constant buffers).
Pro Component based architecture

Pro Extensive learning material
In addition to online API documentation, the Wave Engine team provides tutorials via IndieDB, plus sample projects and "QuickStarters" via GitHub.

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.

Pro Many components are open source
Several core components and official extensions of the Wave Engine are publicly hosted on GitHub.
Cons
Con Lacks documentation
The API documentation is minimal, there's not many tutorials and the ones that are there are very small and only cover the basics. If you want to learn how to properly use it, you have to ask the community or read the source code and figure it out.
Con Not too many games to showcase it
Con Slow development rate

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 Not many tutorials available
Con Outdated UI
The UI looks like it is from Windows XP days. A refresh is much needed.
