I dont have enouch knowlege to be of use. But your prompt reminded me of this; https://www.youtube.com/watch?v=ohDB5gbtaEQ&ab_channel=unmusedtails

I love that skit. However I wasn't looking to have an argument. I was just tired of typing and talking to people is so much more efficient in terms of learning something.

What’s the rough area of your questions? The JS ecosystem is wide 😄

Are you on the doom emacs discord? @ambirdsall there has volunteered

I am, I'll hop over there and see if they're available later today. Thanks @U043RSZ25HQ.

Compiler/munge / Compiler/demunge just saying :)

user=> (Compiler/munge "a-b-c")
"a_b_c"
user=> (Compiler/demunge *1)
"a-b-c"

oh snap

well

it has two versions of that 😂

if it's not in clojure.core, does it really exist?

user=> (source clojure.core/munge)
(defn munge [s]
  ((if (symbol? s) symbol str) (clojure.lang.Compiler/munge (str s))))
nil
user=>

https://github.com/clj-commons/camel-snake-kebab

For “retry on errors,” I recall seeing a clojure wrapper over Resilience4J or something like that. I don’t know of any equivalent for clojurescript unfortunately

But the Resilience4J wrapper is very nice because it lets you define your own retry strategy as data and it comes with other fancy things like rate limiting

And I would quibble with the "clojure" in the wry observation "every clojure project ends up with an ad-hoc ... retry-on-errors function". If that seems new with Clojure, we need to remember the pre-Clojure days when robustness was such an advanced-level achievement that people didn't really expect it

Bit late to the party, but I (not-so-) humbly suggest my https://github.com/KingMob/TrueGrit library, if anyone needs a retry-on-errors fn. It's a wrapper around Resilience4j, but R4j requires coordinating dozens of silly Java classes to get anything done, so the wrapper is worth it in this case, I think.

there are a bunch of libraries but when your needs are limited it's so easy to toss in a loop/recur, and most clojure apps I've worked on have done that at some point

Yeah, True Grit/Resilience4j are more appropriate for large, distributed systems. It's less useful at small scales.