(webdev Tory) @worldsendless@qoto.org

In so many ways tech is catching up with #Clojure: JavaScript getting some immutability, React improving hot-loading and tree comparisons, and other stuff, Python with interactive kernel (REPL). What are ways you see #Clojure maintains its lead?

#clojure goals
---
RT @_jonesian
Rails is just as productive 😉 https://twitter.com/chris__sev/status/1554515237981679616
https://twitter.com/_jonesian/status/1554551543935881216

Hmm. I have a lot of respect for theller's work, but isn't shadowcss https://github.com/thheller/shadow-css just reinventing the wheel? I love using gardencss for #clojure #clojurescript #CSS gen, and it works great cljc. https://github.com/noprompt/garden

A fun thread addressing someone's fears that #Clojure devs get pigeonholed. TL;DR: no, but they do get spoiled.

https://i.reddit.com/r/Clojure/comments/wcqhpg/will_clojure_destroy_my_career/

doubt I qualify as a Clojure beginner, but definitely wanted this!
---
RT @borkdude
New Clojure deps.edn project quickstart for beginners

https://blog.michielborkent.nl/new-clojure-project-quickstart.html

#clojure
https://twitter.com/borkdude/status/1553730334742700033

Ah, this might be the game changer for easily bypassing #clojure clojars (when necessary) https://github.com/reifyhealth/lein-git-down

It's Friday night and I am worn out with font-juggling and red asterisks... #clojure .

#clojure We ran into an issue where duplicate input was causing bizarre behavior -- filtering our things was accumulating with each filter, and certain items would continually match our filter regardless of how weird the filter was. Final answer: React (reagent) keys that were not made duplicate-safe! It was those errors we've read about for years but never seen in action. #clojure

#clojure Clojars new security things prevented me from creating a new project, and an hour of reading later and I might be getting it verified today so I can resume work. The security upgrade is a necessary thing with clojars, but it adds real persuasion to the idea that I switch to deps.edn and use direct git sha codes, cutting out the middleman. I would then need to replace the considerable tooling I have in leiningen, though... #clojure

The power of regexps and emacs. Turn copy-pasted strings into #clojure data-structures of three items. This would be much harder without lisp syntax.

Well, that was annoying. Clojure.math/floor must have an opposite, right? But contrary to normal #clojure style, I had to look up the documentation to find out why it wasn't "ceiling"

It seems that unit testing and private functions are opposed by convention in #clojure Cider and presumably other places -- a fact that can make TDD difficult since, hey -- I need to test that each line of the data spec is handled properly, but those shouldn't be exposed to library users. Solution settled on making a quasi-private namespace where we hide things that drive the main api functions -- technically still public, but documented for clients.