classic VS awesome-love2d

Once they grasp some lua basics and I've actually got a little code running but before I do much to make a game. I'd suggest you give them loom my fork includes the documentation with the code. Also a class system either a basic but easy to understand or more featureful.

I can't criticism your implementation at the moment but I want to share a tiny class module for Lua as a inspiration. https://github.com/rxi/classic

(this example uses classic, which is a library I like using for OOP to keep things simple)

I like classic over middleclass: https://github.com/rxi/classic Feels lighter weight, like barely anything.

You can do oop in Lua too! You just need a class lib.

I'd recommend spending a bit of time with the readme for classic: https://github.com/rxi/classic

Get as simple as possible OOP library, for example this one and write some code using it. This library can inherit ordinary functions, but not any metamethods. Try to improve it. If you can implement metamethod chaining inheritance that allows you to __call an instance of inherited classes like a function, then you understand metamethods thoroughly. Even if you fail, it still will be a good practice.

I tried both and honestly the experience with love is better because it's actually made for lua. There's a vscode extension for love, a ton of lua libraries etc.

For OOP, look into metatables. I got started with Lua through Love2D and through that I found some OOP modules that are pretty helpful. Here’s a full list of them: https://github.com/love2d-community/awesome-love2d (I’ve been using classic with my projects)

Such a great Lua gamedev framework! And there's lots of libraries in GitHub. Many collected on awesome-love2d so you don't have to build everything yourself.

love2d is open source and runs on PC and phones. Someone's even ported it to Nintendo3DS/Switch homebrew. nata is the ECS I use, but you can also checkout more libraries on awesome-love2d. I really enjoy using love2d (especially if you enjoy the engine building parts), but one caveat is that major version number bumps will break compatibility. It's usually easy to port and they deprecate functions long in advance. But there's lots of old libraries out there for older versions that won't just work on the latest love2d (like the code for Harvard's CS50 course).

This is example is just the simple version, a state managers can be very powerful, some examples can be found here

I've used tiny ECS a bit, and I like it a lot. Check out this list

It depends on what you want to display that will dictate the limitations on how you can adjust to different resolutions. There are probably libraries that can help you with this.

Once you've done a few tutorials, you can start doing your own thing. Use the LÖVE Wiki (first link) to your advantage. It has the whole love API documented, and you'll probably need to have it open while you work. At this point, you can also look at this GitHub repository for a list of cool libraries that work with LÖVE.