Comments (3)
The primary problem is still knowing whether the performance impact of memoizing the calculation is less than the performance impact of running the render function again.
One thing I do have on an alpha branch are some macros that will automatically detect what dependencies to add to the array we give to React's useMemo
/ useEffect
/ etc. Something like:
(use-memo
[foo] ;; <-- normal use, passing in a vector of deps to give to React for memoizing the calculation
(+ foo 1))
(use-memo
:auto-deps ;; <-- tells macro to detect and add dependencies in the calculation automatically
(+ foo 1)) ;; <-- macro will detect that `foo` is used in this and add it to the deps passed to React
Re: mobx. Mobx works similar to Reagent, and the way they are able to optimize renders is by tracking state outside of the render tree. The same thing can be done with hx, but it comes with some drawbacks. The pure React way focuses on keeping state within the render tree and aggressively annotating our components with memo when needed, I don't think hx
can get around that yet.
from hx.
I see, thanks for clarifying.
the biggest issue imo is not one-off declarations / nesting props but trying to use Context API for global state management, since all consuming components render for on any state change, regardless of whether their using the state. and it'd be great not to have to always use use-memo
when consuming a context provider
maybe like the use-memo :auto-deps
, there can also be a create-context
utility for overcoming the above issue. react-tracked and constate are examples I've been looking at
from hx.
I've thought about this some more and I like what you're thinking about re: Context.
I think that this should still be opt-in, but can be made much more ergonomic with some syntax sugar.
What I'm currently playing with in my head is annotating expressions with metadata, which the defnc
macro could then inspect and expand into a call to use-memo
or use-callback
. For instance:
(defnc MyComponent []
(let [state (hooks/useContext global-state-context)
foo (:foo state)]
^:memo [:div foo]))
Which would be expanded to:
(defnc MyComponent []
(let [state (hooks/useContext global-state-context)
foo (:foo state)]
(hooks/useMemo
(fn [] [:div foo])
[foo])))
from hx.
Related Issues (20)
- Destructuring defnc :keys [class] has weird behaviour HOT 1
- Improved react dev-tools support for hooks HOT 3
- CLJS data structures are compared by ref in <-effect deps HOT 11
- Semantics and API of <-state HOT 16
- class & className issue when wrapping defnc component with pure react component HOT 3
- Make it fast
- Experience Report HOT 7
- Reducers dont support Multimethods HOT 4
- Document hiccup parser API
- hx/f exceptions handlint HOT 4
- any HOT 1
- Export hooks under Clojure-style names HOT 2
- `defcomponent` API is very confusing HOT 1
- How-to contains misleading memo use HOT 7
- Push missing tags + maybe a 0.5.4 release HOT 2
- Docstring support for defnc (and defcomponent) HOT 1
- Passing down original js props in render props does not work with js->clj
- hx.hooks/useMemo deps as CLJS collection? HOT 1
- Typo in package 0.5.3 (maybe broken) HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hx.