An alternative is Joker: https://joker-lang.org 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 :)
51–60 of 106 posts
An alternative is Joker: https://joker-lang.org 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 :)
Earlier quoted context omitted.
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).
What made you stop using Clojure? Lack of Clojure jobs? Or something else?
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.
jvm clojure's startup tax is exactly why it never cracked the serverless/cli niche, and this pure-go implementation is the kind of unhinged side project, good luck
This is beautiful, makes me wish I'd made it. Excellent work, thank you for sharing it with us ^_^
I wish this had a better language name than just "lets-go". How about "clogo" ?
(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 :)
Earlier quoted context omitted.
What made you stop using Clojure? Lack of Clojure jobs? Or something else?
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 funda…
> I did have some issues with how Clojure is managed
Yes there was some drama a few years back and then Rich wrote his post 'Opensource is not about you'. It was a good post.
Opensource is not easy and you might argue the reason why Clojure is so stable and backwards compatible is because of the way it's managed.
Luckily we didn't end up with a scenario where Rich completely stopped. I think there was a recent case of an opensource maintainer (who works in academia) stopping PRs due to an entitled user. Can't remember the project.
But equally, is the current form of stewardship fit for purpose for the next 10 years of Clojure, i.e. to increase adoption by businesses? Don't know. Maybe something can be learned from how Linux is managed. I think Linus experienced similar bottleneck issues back then.
> I’m actually very interested in yank
I think you mean Jank: https://jank-lang.org/ ?
I'm quite excited about Clojure for GO projects.
EDIT: clarity.