A few more questions if you'll indulge me - The most realistic optimization in this respect is trying to keep the _G table clean and uncluttered. Does the Interpreter always check if an identifer is a global before looking elsewhere for it? I just threw all of the data in the game into one global va...

Hey there and welcome to the forums. So, let's say your player only does ones thing, he prints "HEY!" to the console. the file for your Player.lua would look like this: local Player = {} function Player:talk() print('HEY!') end return Player then to call this file in another file, do this:...

Cool game, and kudos on getting Love.js working. Was it difficult?

Yeah, I should have also said: Definitely just do little projects/experiments to get comfy with the API and whatnot. I just suggested it because a common pitfall for Love newbies (I think) is that a little game comes together, but without too much structure for different pieces of code it turns into...

Thanks for the detailed and reassuring answers. Maybe part of me was waiting for the other shoe to drop in terms of Love's performance, and it's nice to see it holding up as I continue to use it. And use my profiler instead of trying to predict what is slowing down your game I've already been using ...

If you have a decent amount of programming experience, which it sounds like you do, I very highly recommend this tutorial series by recursor. It's long, like 42 hours or something. He builds a really nice ECS system up from nothing and explains everything extremely well, sometimes does some accents....

How much faster do you think it would be than a Löve game that doesn't have any NYI functions? (In other words: a game that takes full advantage of the speed of LuaJIT)

VScode really shines when you install the right extensions. There's a couple really nice ones for Lua support which give you all of Lua's built-in functions and some outlines of tables when you hover over their names, and also a Love2d support plugin by pixelbyte studios that gives you function/para...

Hello All, As my project grows, I wonder more and more how fast stuff is under the hood, and how I should write it to run as fast as possible. My first question is: do tables get slower the bigger they get, or does it not matter because they're just C arrays and hash tables under the hood? To Phrase...

On the topic of CPU usage, I wrote a long post wondering about multithreading, then found the wiki page for it here on the site at love.thread.

I am also wondering: what makes pairs() so slow? Is it something to do with C hash tables under the hood?