Gosu VS Nest

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.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/