Clojurians Log v2
cljsrn
Hi! I’m looking for some opinions from y’all. We have a quite outdated react native app, that desparately needs to be modernized. I’m wondering whether to go the Krell route, or use shadow-cljs (possibly combined with helix). Can I get some pro’s and cons from you? Things that are important to me is integration with Calva, developer experience in general, easy upgradability, and easy use of community packages, both those for RN and generic npm. Really looking forward to your insights!
Reagent suffers from glitches, FWIW.
@hiskennyness What kind of glitches are you referring to?
If you set up the subscriptions a certain way, we see a single initial state change propagate twice to some final subscription. This is the classic "glitch" in reactive programming, where the final dependency has two paths thru the dependency graph to some original node. https://en.wikipedia.org/wiki/Reactive_programming#Glitches
re-frame de-dups the dependency graph so it avoids glitches, or at least I was unable to force one. I ran into glitches in my own Cells/Matrix code when implementing a RoboCup client, which was a brutal use case because all dataflow ran from a single node in which a new game update was received. It totally broke the app.
ps. Yes, I was able to force a glitchy behavior in Reagent. Reported it in that channel ages ago.
For other reasons I would still be building using re-frame if I use Reagent.
Is Expo an option? If that you should have that in the mix of options as well. 😃
I suspect that your choices are more going to be based on your preference rather than some technical issue.
@pez Nope, Expo is not an option.
@dotemacs So what’s yours, and why? 🙂
I like shadow-cljs because it just works. Sticking to it because you can use it for plain cljs projects.
Nothing wrong with Krell either, but I was using shadow-cljs before Krell came out. So I guess you can say that familiarity with it sways me.
Yeah that makes sense.
Since you are a Calva user you already reveal that the purity of each tool doing just one thing is not your primary selection criteria. 😃
The shadow-cljs inspector is totally wonderful. I tap> like crazy these days.
I guess I’m pretty pragmatic in that respect 🙂 And indeed, shadow-cljs’s tap inspector is very convenient. Also head about djblue/portal today by the way, will have to check that out as well, sounds interesting.
One thing I missed from figwheel was that it reports which files are being reloaded. Thomas Heller helped me figuring out a build hook for that:
(defn print-compiled-files
{:shadow.build/stages #{:flush}}
[{:keys [build-sources] :as build-state}]
(let [compiled
(get-in build-state
[:shadow.build/build-info
:compiled])
output
(->> rc
:resource-name
(for [src-id build-sources
:when (contains? compiled src-id)
:let [rc (get-in build-state
[:sources src-id])]])
(sort)
(into [:compiled]))]
(binding [clojure.pprint/*print-right-margin* 20]
(clojure.pprint/pprint output)))
build-state)Did you really mean “figwheel” just now, or shadow-cljs? @pez
I meant that figwheel does this, but shadow doesn’t, out of the box.
Ah right 👍
Regarding helix, there was some discussion in #clojure-europe yesterday regarding frontend frameworks. Some good arguments for Reagent where posted.