LÖVE

I would like to know if there is an alternate to .love on linux. so i don't have to release my sourcecode. Thanks!

Actually, when you release as a .exe, I can view your source code, because zip encodes from the back. So, I can just rename the exe to a zip and open it just fine.

If you want to protect your code, Lua has a compiler (luac), which will turn your code into a binary format that I can't read. Plus, that'll work on every platform, so you can just give me the .love and not have to bother with the .exe alternative.

Inny wrote:If you want to protect your code, Lua has a compiler (luac), which will turn your code into a binary format that I can't read. Plus, that'll work on every platform, so you can just give me the .love and not have to bother with the .exe alternative.

No it won't. Luac-compiled bytecode is not compatible between 32 bit and 64 bit versions of LÖVE. It is not compatible with any LuaJIT version of LÖVE either. Additionally, there are several tools that will decompile Luac-compiled bytecode into mostly useable source code, so there's not much point to all that hassle anyway.

LuaJIT-compiled bytecode will run on all architectures, but again is not compatible with regular Lua, nor is it compatible with different non-revision versions of LuaJIT.

LÖVE is totally free, and can be used in anything from friendly open-source hobby projects, to evil, closed-source commercial ones.

I always knew that the last part of this sentence was a joke towards evil companies in quest for an exploitable framework

this is my humble opinion : the best way to close your sources in löve is to take the habit to write incomprehensible functions commented in your personal secret langage or never plan to release anything than a video of your game

slime wrote:

Inny wrote:If you want to protect your code, Lua has a compiler (luac), which will turn your code into a binary format that I can't read. Plus, that'll work on every platform, so you can just give me the .love and not have to bother with the .exe alternative.

No it won't. Luac-compiled bytecode is not compatible between 32 bit and 64 bit versions of LÖVE. It is not compatible with any LuaJIT version of LÖVE either. Additionally, there are several tools that will decompile Luac-compiled bytecode into mostly useable source code, so there's not much point to all that hassle anyway.

LuaJIT-compiled bytecode will run on all architectures, but again is not compatible with regular Lua, nor is it compatible with different non-revision versions of LuaJIT.

My bad, I wasn't aware that the 32 and 64bit bytecodes of Lua were different. I guess it makes sense that they are.

Saegor wrote:this is my humble opinion : the best way to close your sources in löve is to take the habit to write incomprehensible functions commented in your personal secret langage or never plan to release anything than a video of your game

Or, you know, not use an open source/free/libre licence, relying on the law rather than making your source code a puzzle.