Why would you base it off of nLOVE? Wouldn't you want to take advantage of hardware acceleration?

Yeah, I use setMask and just wait for the GC to pick everything up, in my game.

My bad. I can never get away from the select function!

arg (and arg.n and tbl.n and table.getn and all that stuff) was deprecated 6 years ago . It probably won't work. As bartbes pointed out, a second way to write a more correct version would be something like function Grace.choose(...) if not ... then return end local tbl = {...} return tbl[math.random...

See what all the modules do here: http://love2d.org/wiki/love

LÖVE is a tool to make game development easier. It's not a sandbox or modding environment like WoW's Lua API, where they're restricting access in order to prevent people from doing unintended things to their game. When we restrict access to LÖVE features from ourselves, we're just shooting ourselves...

I compiled an Intel OSX LuaJIT build, for those interested: http://dl.dropbox.com/u/4214717/SELoveJIT.zip

As long as each dimension of the image is a power of 2, it shouldn't matter whether it's square or not. An interesting thing to note is that most of the FPS loss for people is probably because there are so many Lua calculations, rather than a graphics issue. I ran it (without vsync) with regular LÖV...

Nothing should explode in your face, however it's generally good practice to only have drawing-related code being called in love.draw, with everything else going in love.update or similar places.

I don't think anyone is debating whether it's a good idea to make things hard for malicious attackers. What isn't a good idea is restricting legitimate features for all of us based on that fear. If someone feels the need to use SELÖVE, that's fine, but don't make the rest of us suffer.