31–40 of 61 posts
Went to the site and could not find info about Lua version support, is LuaJIT still Lua5.1 only these days? I hope it can support newer versions, e.g. 5.4 etc.
Also interesting is that https://luajit.org/status.html now states “LuaJIT is actively developed and maintained” (whereas for the last ~5 years, “actively” isn’t a word I’d have used), and makes reference to a TBA development branch.
LuaJIT is truly an engineering marvel that more folks should adopt.
If it's actively being maintained again, hopefully that will happen.
What I don't quite get is the follow:
"Please note: The main LuaJIT author (Mike Pall) is working on unrelated projects and cannot accept bigger sponsorships at this time. But other community members may be open to sponsorship offers — please ask on the LuaJIT mailing list for any takers."
Also interesting is that https://luajit.org/status.html now states “LuaJIT is actively developed and maintained” (whereas for the last ~5 years, “actively” isn’t a word I’d have used), and makes reference to a TBA development branch.
That's some good news I needed but didn't deserve!
> DO NOT use pseudo-releases or tarballs created by third parties. In particular, automatic tarballs made by GitHub and other mirrors are lacking the .git directory and will not properly build anymore. It's a little concerning that their build process relies on a .git directory being present. That's going to make it quite tough for packagers to actually package this.
Also interesting is that https://luajit.org/status.html now states “LuaJIT is actively developed and maintained” (whereas for the last ~5 years, “actively” isn’t a word I’d have used), and makes reference to a TBA development branch.
> DO NOT use pseudo-releases or tarballs created by third parties. In particular, automatic tarballs made by GitHub and other mirrors are lacking the .git directory and will not properly build anymore. It's a little concerning that their build process relies on a .git directory being present. That's going to make it quite tough for packagers to actually package this.
I'm confused what you mean. What is a packager doing here? I always assumed that the intention of this library is that you, as a developer, compile and embed it in a product that needs a scripting engine. What use would a standalone LuaJIT package be?
In case anyone is wondering how highly performant / scalable LuaJIT is - Cloudflare was built on top of LuaJIT for the first ~10 years of it's existence and it's only been in the last couples of years they have begun to use Rust.
Also interesting is that https://luajit.org/status.html now states “LuaJIT is actively developed and maintained” (whereas for the last ~5 years, “actively” isn’t a word I’d have used), and makes reference to a TBA development branch.
This makes me soooo happy to hear because with all of the forks of LuaJIT post it not being maintained by Mike ~5 years ago, no one seems to carry the baton very well. LuaJIT is truly an engineering marvel that more folks should adopt. If it's actively being maintained again, hopefully that will happen. What I don't quite get is the follow: "Please note: The main LuaJIT author (Mike Pall) is working on unrelated proj…