Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Loom SDK vs Gosu, the Slant community recommends Loom SDK for most people. In the question“What are the best 2D game engines?” Loom SDK is ranked 45th while Gosu is ranked 50th. The most important reason people chose Loom SDK is:
Loom can live update changes in realtime, allowing you to see them on multiple devices immediately.
Question Ranking
Pros
Pro Live reload of code and assets across multiple platforms
Loom can live update changes in realtime, allowing you to see them on multiple devices immediately.
Pro Powerful command line workflow
Loom Turbo ($5/mo) gives access to powerful command line tools. For example, "loom new" to make a new project, "loom run" to run it. Packaging, deploy, and live reload are done automatically for you.
Pro Open source
The Loom runtime and LoomScript compiler are open source, with code available on GitHub, allowing you to have the freedom to fix the bugs and add the features your game needs.
Pro Examples
Loom includes over 30 examples ranging from complete sample games to demos of single features.
Pro Familiar and powerful scripting
Loom's scripting language is immediately familiar if you know JavaScript, ActionScript, TypeScript, C#, or Java. Internally, it uses a proven VM technology with over 10 years of heavy use in games.
Pro Good support
Loom devs are helpful.
Pro Cross-platform
Loom can deploy to Windows, OS X, Linux, iOS, Android (including Nook, Kindle Fire and Ouya). There are also custom port available for WP8, Blackberry and consoles.
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
Cons
Con Documentation is lacking
Con No visual tools support
There's no level editor, asset viewer or any other visual tools in Loom SDK. Everything has to go through command line. I think it's fine if you really like typing.
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.)
