Listening to a webdev podcast I enjoy, whenever the show runners bring up Typescript (all the time), I mentally substitute #Clojure specs. #gradualtyping
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.
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
I've been looking for certain #clojure swag. I finally found some! https://www.teepublic.com/mask/8637677-clojure-programming-language #FaceMask #ClojureMerchandise
RT @fndriven
In the past weeks I had fun with biff. It taught me a ton abt backend programming. I upgraded my project several times with no problems. Only problem was me trying to fight the framework bc I'm only used to do SPAs. Time to remove the printlns. #Clojure https://biffweb.com/
RT @borkdude
Rich Hickey's view on static types as a modeling language (similar to UML):
My newly refined systemd deployment method for uberjars #clojure #java https://orys.us/uv
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?
RT @SeanCorfield
Shout out to Ning Sun sunng for https://github.com/sunng87/ring-jetty9-adapter/ great #clojure Ring adapter for Jetty 11 w/WebSockets (despite the 9 in the name). Very responsive OSS maintainer! #moa
RT @borkdude
Wanna install the Clojure CLI as a binary clj.exe (no Powershell module) on Windows using an MSI installer?
#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?
Full Stack Clojure web app engineer