(webdev Tory) @worldsendless@qoto.org

Listening to a webdev podcast I enjoy, whenever the show runners bring up Typescript (all the time), I mentally substitute #Clojure specs. #gradualtyping

Cloth over-masks dramatically reduce glasses-fogging #clojure #masks #glasses

A blog post on our #Clojure usage in the Office of Digital Humanities.
https://orys.us/uB

Finally used fnil in #Clojure: to extend a function to support nil case without NPE-ing you! My use: a function that needs to handle strings, collections, or nil, and doesn't know which it will get.

I oversaw the creation of a #PHP #CRUD app for room #scheduling five years ago. It has been good, and has been in heavy use since then -- but suddenly has some issues, probably from #SQL logic -- and I desperately want a #REPL a la #Clojure.

The data coming through the pipeline on one view was missing a crucial piece. It was sweet to be able to add it to the back-end function that is gathering the data, evaluate the form, and boom! It was there for my front-end view as soon as I used my usual endpoint. #Clojure #ClojureScript #FullStack #repl

Every time I have to resort to using a string selector in #clojure #garden #CSS, I feel dirty.

I have my #clojure #timbre #logging to both a file and database. It appears to just STOP after a few minutes of operation -- but we have no idea why. Restarting fixes it for a few minutes. WHY?

I've been looking for certain #clojure swag. I finally found some! https://www.teepublic.com/mask/8637677-clojure-programming-language #FaceMask #ClojureMerchandise

My newly refined systemd deployment method for uberjars #clojure #java https://orys.us/uv

A great #clojure discussion of #XTDB and others vs standard SQL. https://teddit.net/r/Clojure/comments/yj1oah/open_source_datomic/

I have had several problems lately where I never come to understand a "why?" but have a good work-around.

In #clojure reagent (react), why was stuff having bizarre browser focus errors if I PASSED a value from my front-end DB, but fine if I gave it the info to retrieve that value itself?

#Clojure VSCode Cursive seems to roll with the "one repl window to rule them all" approach on full-stack projects, with changes by context. I've seen recent Cider has that option, too, but I much prefer having separate buffers for my CLJ and CLJS repls. Who prefers the unitary version and why?

In #clojure, select-keys against a set instead of a vector must be better or worse. Does using a set actually help? `(select-keys {:foo 1} #{:foo})`

#clojure Logic: "if it's not an atom, make it one." Note that `atom?` is not in core.

I'm not ashamed but can anyone think of more elegant way to do this?