Profile picture
, 3 tweets, 4 min read
My Authors
Read all threads
Looking for twitter account recommendations at the intersection of design, programming environments, cognitive research, and education.

In other words, looking for folks researching how people think about code, and/or creating tools allowing to see it or learn it differently.
Here are a few of my recent follows in this and adjacent areas @katieirenec @girba @redblobgames @yifanwu @drewmikehead @disconcision @dm_0ney @supercgeek @geoffreylitt @neurocy @spiralganglion @warianoguerra @opeispo @azlenelza @CedricSoulas @chrisparnin @aroobacs
One thing I’m seeing is that there is very little intersection between the front-end community and the folks doing this research. This is a huge gap that must be bridged IMO. People creating tools have a lot to learn from them.
Missing some Tweet in this thread? You can try to force a refresh.

Keep Current with Dan Abramov

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

More from @dan_abramov see all

Profile picture
Dan Abramov
@dan_abramov
@nomadtechie I think there’s a few questions here that we need to split apart.

1. Is an event system useful (as opposed to just attaching events on nodes)
2. Does it have to wrap native event objects into custom ones
3. Are React's event polyfills still relevant
@nomadtechie The answer to (1) is yes IMO. Event system uses delegation — i.e. instead of a listener per node, we attach it at the top. This is useful for features we care about (like ability to “record” and “replay” events after hydration). Less work on mount. Solves some edge cases too.
@nomadtechie The answer to (2) is probably no and we can probably use native events there. We’re already removing pooling in 17 so they’re very close. There’s some normalization we still do but it’s probably not as important these days or could be polyfilled separately from React.
Read 6 tweets
Profile picture
Dan Abramov
@dan_abramov
@wycats @garybernhardt Oh no, *this* case definitely sucks and is definitely something we often run into. The plan is to have a compiler do this automatically so that it comes up much less often. Unfortunately we haven’t had time to invest into it yet.
@wycats @garybernhardt The other recourse is simply reduce the need for useEffect. I don’t think it’s really the best solution for this case but sometimes structuring code without it is awkward for other reasons. Which we should address.
@wycats @garybernhardt I think this case is a good example of where reactivity is not the right tool. There’s already an explicit signal for when this function should run — the user clicks a button and AJAX response come back. Rederiving this signal through change notifications is lossy by definition.
Read 4 tweets
Profile picture
Dan Abramov
@dan_abramov
@tannerlinsley That’s exactly what I’m saying here. Suspense *as a feature* doesn’t do much, and is already available (it even works with caveats in stable). The point isn’t that feature but the whole picture — reading data anywhere in the tree without ceremony. That requires a cache.
@tannerlinsley When we say “Suspense for data fetching” we don’t mean “the Suspense component”. That’s been done over a year ago. We mean an integrated and flexible solution that lets you write code in that paradigm.
@tannerlinsley This solution includes: a way to read data anywhere in the tree, a consistency guarantee (if parent and child both read some data for new ID, you don’t show old+new mixed up), a cache layer to avoid waterfalls, an invalidation strategy, plus a code splitting integration.
Read 16 tweets

Embed code for your website

×
Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!