marcingas

The JVM itself - yes, but then you need to wait for Clojure itself. Clojure is famously slow because it interns a bunch of stuff and computes var references every time it boots. I never intended for let-go to be a race car but small distro, low memory usage and snappy start are its priorities at the moment.

Updated. Looks like my VM gets a beating from wazero but that's kind of expected :D

There is one being made in C http://mino-lang.org/

Naming is hard but I like let-go, it's a layered pun :)

(let [...] (go ...))

It lets you let in Go!

Clogo is a no-go for me. Maybe you have some other ideas? I'll consider good ones :)

Thank you! If you ever want to contribute PRs and issues are warmly welcomed :)

Thanks! I've been looking into custom runtimes for AWS Lambda and I think it's not going to be hard to have let-go lambdas. Even though the language is not 100% compatible it should be enough for request handlers and data processing. Throughput isn't on par with JITed impls but it's not bad enough to be impractical IMO

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 :)

Fixed, thanks! It's 6-7ms on my machine. Median seems to be around 6.5ms :)

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.

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!

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

No worries at all. I understand your point. I'll look into fixing this!

Good question, perhaps I really was just careless. I'll look into fixing the README.

Thanks for feedback. Here's a pre-AI-slopped README https://github.com/nooga/let-go/blob/98c2e2ebf38519bceb4f799...

You can also refer to the HN post itself - it says why I think it's cool.

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.

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?

Added https://github.com/chr15m/awesome-clojure-likes/pull/27 Thanks for letting me know :)

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.

Thanks for kind words! Please don't forget to drop me an issue or two when you eventually get to it :)

Yes, I know about this one. I'm even comparing against it in my benchmarks :)

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".

hey, I made this :D

Thanks for posting :)