injest VS xforms

joinr pointed out this lib to me and it seems to make using them more ergonomic (if you're into pipelining)

https://github.com/johnmn3/injest

However writing your own indeed doesn't sound fun :))

As I posted on Reddit:

It might also be good to mention Injest

https://github.com/johnmn3/injest

Which makes transducers more ergonomic to use if you are like me and use threading macros everywhere

Would be curious to hear how others feel about it

If you don't know how to use transducers, I recommend trying: https://github.com/johnmn3/injest it automatically converts your normal sequence operations to make-use of transducers.

You can use https://github.com/johnmn3/injest to get threading macros that use transducers.

In this 2021-11-22 workshop, John Newman introduced Injest.

The transducers workshop by Ben Sless is recommended as background for John Newman's workshop about Injest, which will take place a week later. https://github.com/johnmn3/injest

profile and test. sometimes the lazy path is fine, but in general, transducers should be more efficient. there's a recent library that tries to make it somewhat seamless to go between the threading functions with lazy seqs or transducers, called injest.

Maybe https://github.com/cgrand/xforms The for transducer might help, just as the for comprehension helps unpack and map/filter nested stuff.

cgrand/xforms is a very useful hidden gem, if you like transducers/eager evaluation/solving map-vals without meander/specter.

* It's fast enough for 99% of apps out of the box. It's fast enough for 99.99% of the apps with minimal tuning.

* Yes, if your project is very big and macro heavy, it can take some time, but startup times have improved. In any case, I BARELY need to restart my development JVM. I have one currently running that I haven't restarted for 1 week+.

* Depending on what's your cup of tea, there's emacs/CIDER or IntelliJ/Cursive. They both work well. IntelliJ/Cursive is an excellent IDE combination. I use it every day.

* Java interop is very straightforward, not sure what you mean. Sure your code might not be all pure anymore, but that's the price for solving actual problems.

* Good java libraries have wrappers. A ton of original Clojure libraries as well. https://github.com/cgrand/xforms for example allows you to easily do things that I can't even imagine doing in an imperative language.

* Static vs dynamic typing: don't want to get into that.

* "Clojurescript isn't the same language". I use both Clojure and ClojureScript every day and as far as Clojure-only code is concerned, it works in both languages 99.99% of the time. One case you can encounter issues is if you do something host-specific, like dealing with numbers. That's by design. Clojure embraces each host, does not try to reinvent it. When you just use pure Clojure data structure manipulation, it works the same across both languages and works like magic.