You should see how fast libc gets mmaped() into the VM and the first instr runs :)
marcingas•May 9, 2026
Sure, I should clarify: The 7ms here is measured at the point where let-go starts executing user code. It takes 7ms to initialize the compiler, load all stdlib namespaces and compute all vars. So it's not "time to first instruction", it's "time to running your code".
Yes, I know about this one. I'm even comparing against it in my benchmarks :)
rcarmo•May 10, 2026
You need to update the go-joker numbers, I removed the GIL yesterday or so and did some changes to the IR. ;)
marcingas•May 10, 2026
I think I've pulled the latest today but will double-check and update them again tomorrow. I'm still puzzled why it doesn't run the tak function. Btw. Have you tried running my benches? I'm very curious about your results!
This is the kind of clojure port that I always was looking for. Mostly because I thought go's core library and channels abstractions hits a simpler/nicer base API which would with the core & async apis (not to mention scratches my big beautiful binary itch)
Thanks for your work will definitely check it out again once I get over renewed love for cpp (26)
Edit how did glojure go under my radar also a great project from the looks
marcingas•May 9, 2026
Thanks for kind words! Please don't forget to drop me an issue or two when you eventually get to it :)
giancarlostoro•May 9, 2026
I have played with the idea of making a “old school PHP” style DSL that takes advantage of the Go runtime and packages under the cover. I say old school PHP because PHP used to be a web focused DSL its no longer the case, I feel like it would make for an interesting easy to use backend language similar to PHP but with the full power of Go behind it. Clojure is an excellent choice.
Gloat is a Glojure AOT automation tool.
I worked with James Hamlin to get Glojure AOT going last summer and have been moving it forward since. I've also been working with marcingas (nooga) to get Gloat/Glojure/let-go all cooperating.
asdfasd323f•May 9, 2026
obviously vibecoded
marcingas•May 9, 2026
Yes, I have used AI to boost Clojure compat and fill out some blanks but the runtime itself is not vibecoded. I wrote it myself between Jan 2021 and July 2023. All commits on GH.
blanched•May 10, 2026
You made an account just to post this low effort “criticism”? What’s the point?
adi_kurian•May 10, 2026
Is it bad? Did you try it?
asdfasd323f•May 10, 2026
The readme clearly has abundant emdashes and emojis everywhere, the code itself is obviously vibed. Not really sure what you're objecting to, to be honest.
marcingas•May 10, 2026
Yeah, it has em dashes alright. But the emojis you're referring to were committed in January 2023 (0c4925c). But that's besides the point I guess. What is your point?
asdfasd323f•May 10, 2026
My point is your project is a piece of shit.
jeremyjh•May 10, 2026
Did you even look at the repo history? Clearly it blasted off this year that way but that isn't how it started. Probably he got way more into it once he could make faster progress on all the yak shaving required to make it more useful.
asdfasd323f•May 10, 2026
I did. And it looks like you did too. Which is why you answered your own question in the second half of your comment, quite amusingly. "Probably" LOL!
Macros with syntax quote,
Reader conditionals,
Destructuring,
Multi-arity functions,
Atoms, channels & go-blocks a'la core.async,
Regular expressions (the Go flavor),
Simple json, http and os namespaces,
Many functions ported from clojure.core,
REPL with syntax-highlighting and completions,
Simple nREPL server that seems to work with BetterThanTomorrow/calva,
asdfasd323f•May 10, 2026
Fuck off idiot. Lmao. If I saw you IRL i would slap the fuck out of you.
marcingas•May 10, 2026
Yeah, pretty much. I abandoned it in 2023 due to lack of time. At this point it had enough lift for solving AoC problems and writing small scripts. I've recently dusted it off and did the boring parts of the "roadmap" with Claude.
absolutely sick of reading through obviously AI-slopped READMEs. it's your project, take a little pride and tell me why i should like it quickly instead of asking your agent to rattle off a list of features -- it's severely boring & offputting.
You can also refer to the HN post itself - it says why I think it's cool.
j3s•May 10, 2026
apologies if i was blunt - readme sloppage is a particular annoyance of mine that is quickly becoming common. i'm not against vibecoding, far from it. but a readme is a part of a project that humans immediately touch - seeing it littered with em-dashes signals carelessness.
i appreciate you taking my feedback with grace.
marcingas•May 10, 2026
No worries at all. I understand your point. I'll look into fixing this!
rcarmo•May 10, 2026
I would like to point out, again, that em dashes are very much used by humans that run macOS or iOS — like in this case.
stingraycharles•May 10, 2026
Why did you feel the need to slopify your README? The original version read much, much better.
I genuinely don’t understand why people do this.
marcingas•May 10, 2026
Good question, perhaps I really was just careless. I'll look into fixing the README.
stingraycharles•May 10, 2026
It’s all good. Your project is awesome (and I say this as someone who has done Clojure fulltime for 5 years and nowadays write mostly Go).
uxcolumbo•May 10, 2026
What made you stop using Clojure? Lack of Clojure jobs? Or something else?
stingraycharles•May 10, 2026
Job offer I couldn’t refuse that didn’t have Clojure.
Now I work for a fully remote team, can work anywhere in the world, at any moment I want, leading the data / cloud team for a distributed timeseries database.
Can’t complain. :)
Clojure has had a huge, fundamental impact on my way of approaching software development. I actually came from a Haskell / C++ background, but the way Clojure treats data still has a fundamental impact on how I reason about data, architecture and simplicity.
I did have some issues with how Clojure is managed and do not always subscribe to Rich’s vision (I think core.spec makes no sense, a heavily macro based global state registry is fundamentally not how I would design this, and malli is infinitely better. same for core.async vs manifold), but that is a minor detail in what was a transformative experience for me.
I believe I am not alone when I say this.
I’m still following things from a distance. Considering the current thread, I’m actually very interested in yank, which is Clojure on LLVM, and have been sponsoring that project for a few years. That would be very nice if it could enter stable state, I may take another look again.
jimbokun•May 10, 2026
This version is infinitely better.
faangguyindia•May 10, 2026
I am finding i need "Rails" but i like single binary deployment of Go and fast/low resource usage like Go.
Is it possible for now?
marcingas•May 10, 2026
I think you could make a framework on top of this. It doesn't yet run unmodified Clojure libs like hiccup but it wouldn't be hard to roll something relatively simple and solid in let-go. IMO
As far as JVM-free Clojure-like, Janet is really nice. I've been using it in production for a while: https://janet-lang.org/ There's also Fennel if you want the Lua vm and libraries.
marcingas•May 10, 2026
Thanks! Joe looks good! As for Janet - never tried it myself but I always thought it's doing its own thing instead of trying to be Clojure.
TJSomething•May 10, 2026
While Janet pulls from a few inspirations, the syntax is pure Clojure. I always figured that it was trying fix up the bumpy parts in Fennel to enable a programming style that was more consistently Clojure-like and functional than could be done in Fennel, since Fennel ultimately has to use Lua's semantics because Fennel compiles to Lua.
boguscoder•May 10, 2026
Micro nit: it says 7ms cold start and then 6ms just few lines lower.. maybe it gets faster as you read README
marcingas•May 10, 2026
Fixed, thanks! It's 6-7ms on my machine. Median seems to be around 6.5ms :)
I think it is brilliant and completely underappreciated :)
marcingas•May 10, 2026
What I appreciate about Joker is how smoothly it wraps Go libs. It seems that they have covered everything that Go has to offer.
I'm trying to avoid adding too much though, I like that let-go fits in 10MB :)
lenkite•May 10, 2026
I wish this had a better language name than just "lets-go". How about "clogo" ?
achenet•May 10, 2026
This is beautiful, makes me wish I'd made it.
Excellent work, thank you for sharing it with us ^_^
phplovesong•May 10, 2026
There seems to be a surge in compile to Go projects recently. To me this signals that the runtime / stdlib of Go is one of the best out there (when going the GD'd route), but the surface level (syntax) is too simple/verbose and lacks the expressiveness developers want.
So far Lisette (http://lisette.run) seems to be the best/most active version of a compile to Go language out there.
14 Comments
https://github.com/glojurelang/glojure
Thanks for your work will definitely check it out again once I get over renewed love for cpp (26)
Edit how did glojure go under my radar also a great project from the looks
Gloat is a Glojure AOT automation tool. I worked with James Hamlin to get Glojure AOT going last summer and have been moving it forward since. I've also been working with marcingas (nooga) to get Gloat/Glojure/let-go all cooperating.
https://github.com/nooga/let-go/tree/d9dc094822b2983ebf44604...
In 2023 he had a working Clojure compiler with:
Macros with syntax quote, Reader conditionals, Destructuring, Multi-arity functions, Atoms, channels & go-blocks a'la core.async, Regular expressions (the Go flavor), Simple json, http and os namespaces, Many functions ported from clojure.core, REPL with syntax-highlighting and completions, Simple nREPL server that seems to work with BetterThanTomorrow/calva,
You can also refer to the HN post itself - it says why I think it's cool.
i appreciate you taking my feedback with grace.
I genuinely don’t understand why people do this.
Now I work for a fully remote team, can work anywhere in the world, at any moment I want, leading the data / cloud team for a distributed timeseries database.
Can’t complain. :)
Clojure has had a huge, fundamental impact on my way of approaching software development. I actually came from a Haskell / C++ background, but the way Clojure treats data still has a fundamental impact on how I reason about data, architecture and simplicity.
I did have some issues with how Clojure is managed and do not always subscribe to Rich’s vision (I think core.spec makes no sense, a heavily macro based global state registry is fundamentally not how I would design this, and malli is infinitely better. same for core.async vs manifold), but that is a minor detail in what was a transformative experience for me.
I believe I am not alone when I say this.
I’m still following things from a distance. Considering the current thread, I’m actually very interested in yank, which is Clojure on LLVM, and have been sponsoring that project for a few years. That would be very nice if it could enter stable state, I may take another look again.
Is it possible for now?
As far as JVM-free Clojure-like, Janet is really nice. I've been using it in production for a while: https://janet-lang.org/ There's also Fennel if you want the Lua vm and libraries.
I think it is brilliant and completely underappreciated :)
I'm trying to avoid adding too much though, I like that let-go fits in 10MB :)
Excellent work, thank you for sharing it with us ^_^
So far Lisette (http://lisette.run) seems to be the best/most active version of a compile to Go language out there.