This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-02
Channels
- # announcements (4)
- # babashka (1)
- # beginners (4)
- # cider (4)
- # clerk (3)
- # clojure (25)
- # clojure-brasil (5)
- # clojure-europe (6)
- # clojure-nl (1)
- # clojure-norway (48)
- # clojure-uk (4)
- # clojuredesign-podcast (3)
- # clojurescript (1)
- # conjure (1)
- # emacs (23)
- # hyperfiddle (3)
- # jobs (6)
- # lsp (12)
- # off-topic (5)
- # polylith (13)
- # reagent (8)
- # reitit (18)
- # sci (20)
- # shadow-cljs (8)
- # specter (3)
- # squint (3)
@neumann I’ve been meaning to post this for weeks — my feeling listening to your latest series is that you’ve been watching me slog thru the mud for the last three months. 😂 😂 Long running API calls to OpenAI, or transcribing videos in RevAI, or downloading emails from Gmail, or fetching videos from Google Photos, or fetching videos and extracting videos in ffmpeg, or testing URLs for liveness. Long sessions in the REPL, plowing forward, trying to figure out what in the heck Google Java clients return, dealing with rate limit issues, long “iteration” calls, attempts to cache values for speed (and occasionally biting in the butt)… running into totally unexpected error cases as I start doing longer runs, trying to figure out where the try/catches should be. I loved your suggestion of returning maps of all the intermediate values in the “let” bindings. Would save so many “defs” in my code! Can’t wait to listen to this weeks episode!!! (I posted today my recent gobsmacked reactions to the Google Photos Java client here, which made me question my sanity here: https://clojurians.slack.com/archives/C1AC4BU2K/p1706810085720339)
In my experience, Google's APIs tend to be really frustrating and Google's Java APIs doubly so. It's actually quite impressive how they can write documentation that's comprehensive, technically correct and somehow, frustratingly unhelpful. I've definitely abandoned Google's Java APIs for their REST APIs multiple times.
@U6VPZS1EK Out of curiosity, are you using JVM Clojure or #babashka for those things? It sounds like a good use case for Babashka (I'm doing similar stuff). https://book.babashka.org/#tasks is convenient as a "UI" to my Clojure code.