The beauty of Clojure/Lisp is that we have a nice macro system. Over the years, people created their own macros to simulate async/await. This is a powerful feature of Lisp, you don’t have to wait for an official release, you can just add that feature to the language yourself. Now we don’t have to use that custom macro anymore, which basically did the same thing.
I’ve built many different kinds of software (backend, frontend, 3D games, cli tools, code editor, and more) with Clojure and have been using it for over a decade now.
I can confidently say that, among the list I mentioned, it’s the best for data manipulation/transformation. Thanks to the author for presenting it clearly and showing how the libraries and code look across different languages, all of which do a great job.
But Clojure has its own special place (maybe in my heart as well :). I think Clojure should be used more in the data science space. Thanks to the JVM, it can be very performant (I’m looking at you, Python).
Yes, sorry about that if it annoyed you. I was too busy to write a good human-sound readme. It was an old project, and I wanted to release it as open source as quickly as possible.
Hey, thanks for the feedback. Honestly, I don't know. It seemed pretty easy to do that way at that time. But I'd accept PRs that could improve the product.
It looks really nice, but CPU usage is almost 100% all the time. I have a MacBook Pro M3. When I open some fancy Three.js scenes that I found on the net, I instantly profile them. Most of them are really bad in terms of performance. I don't know why.