Pluto is a unique dialect of Lua with a focus on general-purpose programming

Posted by 90s_dev 7/1/2025

Pluto is a unique dialect of Lua with a focus on general-purpose programming(github.com)

77 points | 40 comments

nathan_compton 7/1/2025|

This appears to be a pile of syntactic sugar on top of Lua, which is an idea which would have appealed to me a lot as a younger developer. But the older I get the more I realize that its almost never actually syntax or brevity that gets in the way in a software project and that this sort of thing often introduces a lot of cognitive overhead. It isn't that these extra doodads are hard to wrap your head around, but the fact that we have two very similar languages (Pluto, Lua) that we are interactive with on a regular basis (because Pluto works within the Lua ecosystem) and now we have to think about that a lot.

I think a lot of programmers when they first learn Lisp go crazy with macros, adding all sorts of flimflam to their programs because they can, but then eventually you realize that just makes life harder, or at least marginally more complicated, and you gradually give it up. Feels like a similar calculation could apply here.

ryandvm 7/1/2025||

Absolutely agree. In my experience, languages that have multiple forms of syntax for doing the same thing are just laborious to read.

Kotlin has some great ideas, but it's kind of frustrating to have half my code yellow-highlighted because the IDE has detected that there's a short-hand version of everything.

Lerc 7/1/2025|||

I feel like good syntactic sugar should reduce cognitive load.

for example in JavaScript

    let fish = 5
    let cheese = 27
    let nop = 0x4e71

being able to do

    result = {fish,cheese,nop}

Is 'only' syntatic sugar but significantly reduces the cognitive load over

    result = {fish:fish,cheese:cheese,nope:nop}

looking at the latter it is harder to take in the options at a glance, when reviewing you have to check if the names match. If they don't match was it intentional or accidental. Whereas if you encountered

    result = {fish,cheese,nope:nop}

You are left with no doubt that the nope is not a typo but a explicit name specifier.

nathan_compton 7/1/2025||

I don't know, from my point of view having both syntaxes is clearly more to think about, and all you get from the shorter one is typing a few fewer keystrokes.

Philosophically, I feel a little ambivalent about the briefer syntax because it mixes two sorts of denotations. Variables refer to scoped objects for which, from the point of view of what the program means, vanish (in compiled languages they literally can totally vanish - variable references are just resolved into the appropriate reference to memory). The keys of a hash table are totally different sorts of things and persist at runtime. I'd prefer that these two very distinct conceptual spaces remain separate, even if in a certain sense they overlap in a specific case.

Doesn't really matter, though.

Lerc 7/1/2025|||

>I don't know, from my point of view having both syntaxes is clearly more to think about

That's storage, not load. You need you know more, but you don't have to think about as much at any one time.

BrainFuck has extremely simple operations. You don't have to think about very many different things at all, but you need to think about them a lot.

>and all you get from the shorter one is typing a few fewer keystrokes.

I'm not particularly concerned about keystrokes (unless I'm golfing). I'm happy to increase the size of the content to reduce how much I think about it. Reducing the number of elements I have to look at to grasp the same concept is distinct from keystrokes.

Sometimes

   ArbitraryLongVariableName = 43

is better than

   a = 43

one the other hand I'd take

   ArbitraryLongVariableName += 1

over

   ArbitraryLongVariableName = ArbitrarilyLongVariableName + 1

hmmokidk 7/1/2025|||

Low key this is so interesting because in Elixir there was this specific example with a library that extended the lang to do this.

The concise syntax was tossed out, but I have a soft spot for it.

cultofmetatron 7/1/2025||

[dead]

TeddyDD 7/1/2025||

I like the idea of bundling Lua with bunch of batteries but the syntactic changes go too far. They seem to be lousily designed attempt at turning Lua into Typescript.

For example coalescing operator. You can do the same in standard Lua with or. Pipe operator might seem like cool idea, but the language needs to be designed around it (Elixir) or you need multiple variants (threading macros in Lisps).

shayway 7/1/2025||

Yeah, there are a lot of odd inclusions like that; things that overlap or replace standard lua flow for no reason (see ternary expressions[0]). I would love an expanded lua, with built-in classes and a more robust standard library, but this feels more like a rewrite into a new langauge with two vastly different design philosophies layered awkwardly on top of each other. Which it is I guess.

I don't mean to discount the work that has gone into it, and there are a lot of really neat features here. But honestly I think it would be stronger as a standalone thing, without all the lua baggage, given how far idiomatic pluto diverges from idiomatic lua.

[0]https://pluto-lang.org/docs/New%20Features/Ternary%20Express...

Lerc 7/1/2025|||

I'm not a Lua user but is this a falsiness issue?

local function report(result) print(result ?? "The value was nil.") end

report(filesize("/path/to/file/of/length/zero"))

If filesize returns nil for file-not-found and the length otherwise. Wouldn't coalescing work and or would not be able to identify existing but empty files.

90s_dev 7/1/2025||

As a TypeScript fan, I was really happy to read pretty much every one of these changes. This is a language I wouldn't personally use unless it gains massive traction, but one that I hope it gains massive traction so that I can justify spending the time memorizing and learning all these new language additions.

It's particularly exciting that they constantly rebase upstream Lua, and plan to update it to be compatible with Lua 5.5. Especially because Lua 5.5 finally has the ability to turn off globals!

spacechild1 7/1/2025||

Lot's of good stuff in there. My personal highlights:

1. classes

2. named parameters with default values

3. string interpolation

I love Lua, but it's a bit sad that everyone ends up hacking together their own OOP system (including myself). I would really prefer a standardized solution.

Named parameters are such an underrated feature IMO. It makes function calls so much easier to read, in particular if the arguments all have the same type. I know, we can "fake" named arguments by passing a single table argument, but this has some overhead and default values are still rather awkward to implement. The one big downside of named parameters is that the parameter names are now part of the public API.

jay_kyburz 7/1/2025|

In my next lua project I'm going to try and avoid oop and stick with functions and data.

I don't know why, but 100 times a day I have to go back and replace a dot with a colon and it drives me nuts.

wavemode 7/1/2025||

Curious how this compares with Luau: https://luau.org

Rochus 7/1/2025||

Or Luon: https://github.com/rochus-keller/Luon

msephton 7/2/2025||

Lua = OG

Luau = Performance

Pluto = Features

Luon = statically typed

WillAdams 7/1/2025||

Would general-purpose programming include making a Graphical User Interface?

A simple and small language with GUI bindings and a graphical tool for laying out a design in a flexible manner with a responsive result is something a lot of folks would find useful.

Rochus 7/1/2025||

Interesting, apparently the source also includes a (modified) version of the PUC Lua VM. Why don't they just generate bytecode for the existing VM and leave it as is (unless the modified version somehow would significantly increase performance)? What changes were necessary to the original VM to implement the language?

90s_dev 7/1/2025|

Some features like break N and default function args seem to be incompatible with the vanilla lua vm.

Rochus 7/1/2025||

I think that would be achievable with plain PUC Lua bytecode; it's actually just a jump. The same for default function arguments; the VM doesn't actually care how many arguments the caller pushes on stack, and providing default values is easy to implement for the caller.

yungporko 7/1/2025||

i was expecting something dumb if i'm honest but it looks really nice, i would probably use this. it seems like the perfect extension of the "code vomit" speed of writing lua and moves it further in that direction imo.

the thing i like lua for is easily getting into that "flow state" of just writing code without having to think about "how should i approach this" but sometimes the lack of things which pluto addresses forces a level of verbosity that snaps me out of it. i often find myself hitting a mental roadblock where i think "like fuck am i gonna write that much code to do X, i'll just go work on a more fun part of the program and come back later".

yannis 7/1/2025||

Well written and well documented. I will be trying it out. One drawback that I see is the use of packages from LuaRocks might be an issue and one does not really want to cope with compilation issues. But Lua is a beautiful language in any form.

90s_dev 7/1/2025||

Basically a more convenient/intuitive Lua for JS/C/Java/C++ users, plus optional static typing. May in fact use this instead of Lua.

JdeBP 7/1/2025||

There's almost nothing in there that's like C or C++. But there's a definite influence of .NET and C♯ with things like null-coalescing, null-conditionals, and interpolated strings.

Imustaskforhelp 7/1/2025||

Yea. I am definitely trying this out too. It really has some new features changes that I wished lua had.

matusnovak 7/1/2025|

Is it possible to use Pluto alongside with a binding library such as Sol2[0]? I don't mind not being able to set type hints in the bindings to use in some IDE, I can create stubs for it manually.

[0]: https://github.com/ThePhD/sol2

More comments...