alt Hacker NewsJob 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.
Replies
I've never heard of manifold before and I'm curious what you prefer about it to core.async.
I've read through their website and README but I feel like I'm missing what separates it from other async libraries.
Can you explain a few examples where it shines compared to core.async?
Thanks for clarifying.
> 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.