June 24, 2026
Syntax and the City
LuaJIT 3.0 proposed syntax extensions
LuaJIT’s glow-up has fans cheering, critics yelling “this is basically a whole new language”
TLDR: LuaJIT is adding new code-writing shortcuts for version 3.0 and backporting some to the current branch to help build it. Commenters are split between excitement that the project seems active again and panic that it’s drifting so far from Lua that it may need a whole new name.
A sleepy corner of programming just got a surprisingly spicy wake-up call. The big news is that LuaJIT — a faster version of the Lua programming language — is proposing a batch of new writing shortcuts for its future 3.0 release, while also sneaking some of them back into the older 2.1 version to help build the new system. That sounds dry on paper. In the comments, though? Instant identity crisis.
The loudest reaction was basically: wait, is this thing alive again? Multiple commenters sounded genuinely shocked that LuaJIT appears to be moving beyond basic upkeep after years of quiet. But that excitement quickly turned into a naming war. Several people argued that if LuaJIT keeps adding new syntax, it stops being “just Lua, but faster” and becomes a whole new language wearing Lua’s nametag. More than one commenter flat-out asked if it needs a new name.
Then came the true comment-section villain: the ternary operator, a compact if-this-else-that style shorthand. One camp called some of the changes useful quality-of-life upgrades. The other camp reacted like someone had brought pineapple to a funeral. “I see JavaScript,” one person sighed, while another declared they would never understand ternary operators because “chuckle heads” inevitably abuse them and turn code into a nesting doll of misery. The developer explicitly begged people not to spiral into cosmetic symbol debates, which of course only made the whole thing feel even more like a prequel to a beautiful bike-shedding disaster.
Key Points
- •LuaJIT opened an umbrella issue to track and document proposed syntax extensions for LuaJIT 3.0, replacing related issues #63 and #1379.
- •The stated criteria for new syntax are improved developer quality of life, prior proof in other languages or Lua dialects, no ambiguity, backward compatibility, and minimal disruption to tooling.
- •LuaJIT 3.0 is planned as a self-hosted VM written in Lua, creating a bootstrap problem that currently uses LuaJIT 2.1 as a temporary build path.
- •A subset of LuaJIT 3.0 syntax extensions has already been backported to LuaJIT 2.1 to support the 3.0 codebase.
- •The backport is being tested in a temporary branch, temp-v3bp-syntax1, with plans to merge into the official v2.1 tree rather than create a separate v2.2 release.