This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-07
Channels
- # babashka (30)
- # beginners (49)
- # calva (22)
- # cider (9)
- # clara (2)
- # clj-commons (1)
- # cljdoc (1)
- # clojars (7)
- # clojure (153)
- # clojure-australia (2)
- # clojure-europe (45)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (17)
- # clojure-portugal (3)
- # clojure-uk (6)
- # clojurescript (21)
- # conjure (4)
- # copenhagen-clojurians (5)
- # cryogen (3)
- # cursive (19)
- # datahike (14)
- # datascript (4)
- # datomic (9)
- # events (5)
- # fulcro (23)
- # graalvm (1)
- # gratitude (4)
- # helix (2)
- # holy-lambda (5)
- # improve-getting-started (2)
- # jobs (10)
- # kaocha (1)
- # leiningen (1)
- # liquid (8)
- # membrane (81)
- # off-topic (88)
- # polylith (29)
- # quil (1)
- # reitit (2)
- # remote-jobs (8)
- # reveal (8)
- # sci (1)
- # shadow-cljs (14)
- # specter (4)
- # sql (5)
- # tools-build (11)
- # tools-deps (5)
I hoped we could get an almost as good a 👋 streak as in #clojure-nl yesterday but whatevs :-)
Thank you kindly @U0525KG62
it’s plain reagent, but I made some “clever” code to derive state using make-reaction and it’s bugging out
make-reaction is still completely undocumented even though it’s the core of reagent..
@simongray you've probably thought about this, but when using re-frame, using make-reaction
isn't usually necessary. when I find myself needing this, I realize I've reached the reagent -> re-frame size of my project
either I've never reached that size of project or always managed without make-reaction
.
I don’t think it’s a “size of project” thing as much as it is a “kind of project” thing. It’s a library first of all (not a situated application) of adaptive UI widgets where reagent atoms/cursors are used in a fairly idiosyncratic way. I have some utility code for syncing reagent state since I don’t want the library to be dependent on Re-frame. This was the code that was giving me a head ache (now fixed): https://github.com/kuhumcst/stucco/commit/a1126126876f2d78a4ab3bfd168f9d5ae423026e
Basically, the implementation code uses this utility function as a way to bind the index
of two views together. In Re-frame you would create a subscription, but this would be a project-specific solution tied to specific instances, while my library needs a generic way of doing this for any piece of reagent state (ratom, cursor, etc.).
Please folks, let's not assume re-frame is the only natural path from Reagent - re-frame has significant limitations.
yeah, the re-fram equivalent would probably be subscriptions, but I don’t use re-frame for this project
It’s a bit experimental to be honest. Re-frame’s paradigm of a single directed data transformation graph doesn’t really fit the problem space well.
I fixed my messy frontend. Mornings really are best for debugging. Afternoons probably better spent on refactoring.
Perhaps 😛 I find that I spend many afternoons rerunning code attempting to fix a bug before I get off. The next morning that complex issue often turns into a small change.
Morning! Today I’m coding Python, pretending it is 🤓
Today is a “slack” day at the company and I’m experimenting with a library called toolz
that brings functional concepts into the language. Also, I’m converting Clojure code from the excellent talk “Clojure in a Nutshell” by @james to Python. I am planning to write something about this, or recording a short video. Perhaps both 😄
Here’s an 8 minute video, where I have copied James approach and code examples, to try out the functional abilities of Python: https://www.youtube.com/watch?v=VHS9wtNcnE4
toolz looks great! I'm volunteering on a project in Python these days, I might sneak it in some day.
Yesterday, to give myself some relief from the Windows hell I was visiting, I mixed it up with writing myself some zsh functions to make rebasing my git branches from some other branch on origin a bit less error prone: rebob
- rebase branch on branch. 😃 https://gist.github.com/PEZ/f8d1c9d1184efa9e6ea929e7da69efce