Gosu VS sdoc

For the beginning, it will be a simple 2D game library (or glorified SDL wrapper :D), similar to Ruby libraries like https://www.ruby2d.com/ or https://www.libgosu.org/ , albeit with some additional functions typical to 2D games (like scenes, maps, entities, ...) available. This is something I'm still missing in Crystal (there are some bindings for C libraries and some early or abandoned approaches, but that's about it).

Sorry, I just realized that I only linked to Gosu's Linux instructions, but in their wiki there's also a page for Windows and another one for Mac OS.

I didn't use these frameworks but if you want to go with Ruby, I would recommend Gosu, which is more active than Ruby2D (they have a pretty active Discord server). Since it's a bit low-level, you could also use my gem MiniGL which builds on Gosu to make a lot of things easier, and I also actively maintain.

By the way, it's worth mentioning that there's a .deb for Debian-based distros that you can get for free on https://victords.itch.io/super-bombinhas. Also, if you're willing to do a bit more work, you should also be able to run it on Mac - you'd just have to install Ruby and the Gosu and MiniGL gems, then clone the game's repo and follow the Readme.

Hi! I've wanted to create an RPG inspired by the first Paper Mario games for a long time, but having to deal with 3D graphics was always a blocker for me... So I finally managed to create an isometric 3D "engine" using only 2D libraries (Gosu and MiniGL) and I'm happy with the results so far.

Gosu (Ruby)

I've not used it myself in about 5 years but it looks like they have a pretty good tutorial on getting started on their wiki https://github.com/gosu/gosu/wiki/Ruby-Tutorial

Neither, I use Gosu and my own little library, MiniGL.

Once you feel comfortable with both Ruby and Rails, try building a few simple apps on your own by reading the Rails Guides and browsing the Rails API whenever you're stuck.

Hi. I'm a self-taught Ruby on Rails programmer. I have a question about the documentation at https://api.rubyonrails.org. On many of the pages, you'll see methods and their details. Below that, you'll often see examples using different options. This is where I have a question. An example might look like this:

If a method isn't documented in https://api.rubyonrails.org/ it shouldn't be used as we reserve the right to remove or change them at any point.

Rails still holds the top spot in getting things out the door in the shortest amount of time. So many example projects and tons of amazing libraries that are available. They absolutely have the best developer docs in the industry as far as I'm concerned.

https://guides.rubyonrails.org/

https://api.rubyonrails.org/

Phoenix/Liveview is a close second. I would personally use Phoenix/Liveview at this point because since I know that stack pretty well, but it is definitely not as easy as Rails to learn. However, once past the learning phase I think there's distinct advantages especially with Liveview.

Fly.io has a free hosting tier currently. You can also get some free servers through Oracle Cloud.

https://api.rubyonrails.org is your best friend. Check the docs before googling. Instant access to the source of functions. ApiDock is shit but continuously gets to the top of google search results.

For something more in-depth, besides the Rails Guides that have been mentioned already, you could also use the Rails API docs as a reference.

Yeah visit guides.rubyonrails.org if you want to see how to do a particular thing like validations and stuff and use this website https://api.rubyonrails.org/ for seeing method definitions their options etc.. These two websites pretty much conver everything. I specially use the second on pretty frequently. Also I think sublime text is better for ruby on rails than vs code but thats personal preference. The ruby doc website is pretty good to for documentation on rubies standard classes. Like if you are looking for some method to do something for a string you can just search string ruby and this comes up first, it contains all public methods for these classes and is pretty useful.

If you mean the Rails API Documentation, I mainly use it when I use a method I'm not familiar with (eg trying to adapt a StackOverflow suggestion).