Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Gosu vs Genome2D, the Slant community recommends Genome2D for most people. In the question“What are the best 2D game engines?” Genome2D is ranked 47th while Gosu is ranked 50th. The most important reason people chose Genome2D is:
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
Question Ranking
Pros
Pro Lightweight
Gosu is not a game development framework, only a media library that happens to be suited to game development. (Kind of like SDL in the C world.) That means the interface is relatively small.
Pro Mature API, actively maintained and developed
Gosu has been under development since 2001. It is mature and has several toolkits built on top of it to provide additional functionality.
Pro Cross-platform, even mobile, using Ruby
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
Cons
Con Deploying Ruby apps is a mess
Games built with the Ruby to .exe "compiler" do nothing more than extract your source code and Ruby.exe to %TEMP%, then run it. The code is not really compiled at all. The process for wrapping games as Mac apps is a bit nicer, but you'll need a paid Apple Developer subscription to code sign the app, or users will see a warning/error when running your game.
The only way to really compile Ruby is to use RubyMotion, which does not work on Windows and requires a paid subscription on top of the Apple Developer one.
(This Con is not specific to Gosu. Deploying Ruby code has never been fun.)
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
