Fork me on GitHub
#off-topic
<
2023-02-03
>
Drew Verlee04:02:17

would anyone like to voice chat about the javascript ecoystem for a bit? ill donate 5 dollars to a charity of your choosing if you listen to my questions.

bherrmann13:02:16

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

Drew Verlee13:02:04

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.

👍 2
hmaurer14:02:18

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

elken19:02:22

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

👀 2
Drew Verlee19:02:06

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

Samuel Ludwig17:02:27

Would anyone like to share their experiences using http://temporal.io (ideally looking for a variety of settings/workloads/team-sizes)? It's just come onto my radar, and it seems interesting

👀 12
Cora (she/her)21:02:07

it feels like every clojure project ends up with an ad-hoc underscores-to-dashes/dashes-to-underscores function and a retry-on-errors function

clojure-spin 4
Alex Miller (Clojure team)22:02:59

Compiler/munge / Compiler/demunge just saying :)

👍 2
Alex Miller (Clojure team)22:02:50

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

Cora (she/her)22:02:15

it has two versions of that 😂

Noah Bogart22:02:19

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

hiredman22:02:51

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

😂 6
hifumi12307:02:08

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

hifumi12307:02:50

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

phill13:02:41

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

Matthew Davidson (kingmob)06:03:56

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.

2
2
Cora (she/her)12:03:48

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

Matthew Davidson (kingmob)05:03:02

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