Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariGosu vs Ebitengine
When comparing Gosu vs Ebitengine, the Slant community recommends Gosu for most people. In the question“What are the best 2D game engines?” Gosu is ranked 50th while Ebitengine is ranked 59th. The most important reason people chose Gosu is:
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.
Specs
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 Simple
One of the core focuses of Ebitengine is to be simple. The screen is just treated as another image that can be drawn to.
Pro Cross platform
Many platforms are supported, including WebAssembly.
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 Bare-bones
For example, Ebitengine does not have a physics engine; instead games must rely on a separate implementation such as Chipmunk2D.
