Comment by klaussilveira
Comment by klaussilveira 16 hours ago
> declarations for global variables
That's huge. I wish LuaJIT adopted this, or at least added a compile time flag to enable it.
Comment by klaussilveira 16 hours ago
> declarations for global variables
That's huge. I wish LuaJIT adopted this, or at least added a compile time flag to enable it.
Not true. It's getting a constant stream of bugfixes. It's also not "stuck" on Lua 5.1, but is deliberately not following Lua's path, except for some backports. There's also a recent post about how a LuaJIT 3 might work.
https://www.freelists.org/post/luajit/Question-about-LuaJIT-...
Warning: Ridiculous cookie consent banner, needs dozens of clicks to opt out.
OK, then I got some wrong info. If it's stuck at it deliberately, then it's worse. May be someone should fork it and bring it up to date with recent Lua versions. Why is this split needed?
My understanding is that there was a language fork after 5.1. One thing was a complete reworking of how math works. It used to be just floating point for everything but the new idea was to make it like Python 3. So most operations are float/integer with some weird exceptions.
As with any language fork there will be some who stay and others who switch to the new thing. Often a fork will drive people away from a particular language as in my case.
I strenuously disagree. Not every language needs to chase trends and pile on unnecessary complexity because developers want the latest shiny language toys to play with. It's good to have a simple, stable language that works and that you can depend on to remain sane for the forseeable future.
C is a language like that but I fear the feature creep is coming (auto? AUTO??.) JS is a lost cause.
Yeah, I wish someone would pick up LuaJIT development. From what I've heard it in practice isn't developed anymore and is stuck at Lua 5.1 still.