Twitter | Search | |
Matt Huebert
Life is an experiment, please be kind.
1,426
Tweets
540
Following
840
Followers
Tweets
Matt Huebert Apr 13
Precisely
Reply Retweet Like
Matt Huebert Apr 10
Replying to @paulg
it’s the last remaining MacBook with a functioning keyboard, AppleCare is no more, every keypress is Russian roulette—will it now stick forever?
Reply Retweet Like
Matt Huebert Apr 6
Replying to @inkandswitch
This looks fun. Example use case: Last week I worked on some research, involved gathering a couple dozen PDFs, organizing by chronology + topic, reading & annotating each, then choosing excerpts to include in a summary. Ability to ‘lay out’ PDFs spatially + link excerpts = 👍
Reply Retweet Like
Matt Huebert Apr 6
Urban captain, postmodern pathfinder, shepherd of the downtown. She’s got directional sense.
Reply Retweet Like
Matt Huebert retweeted
Ink & Switch Apr 4
Our latest research project: Muse explores how to bring the aesthetic of an artist's studio—personal, informal, flexible, multi-media, malleable—to a digital tool.
Reply Retweet Like
Matt Huebert Apr 4
I want to block the term “hot take” is this possible
Reply Retweet Like
Matt Huebert Mar 28
Replying to @roman01la @theKashey
a slightly more useful fork: this compares the same component, with and without memo. attached images of List component (memoizing is much faster) and Empty component (memoizing is slower).
Reply Retweet Like
Matt Huebert Mar 28
Replying to @roman01la @theKashey
tried it in a fork of your comparison, I added an empty component (a single div) as a baseline of time-to-layout. the two components re-render in different React roots, a second apart. not sure how to use react-production w/ codesandbox
Reply Retweet Like
Matt Huebert Mar 28
Replying to @roman01la @theKashey
hmm. could we start a timer at beginning of render, stop it in useLayoutEffect?
Reply Retweet Like
Matt Huebert Mar 28
Replying to @roman01la @theKashey
so i think this phase would be a significant piece of the equation. if the structure you are looking at in React.memo compares fewer pieces than the number of DOM elements represented by the component (stopping at shouldUpdate of children), then I'd _guess_ memo will be faster
Reply Retweet Like
Matt Huebert Mar 28
Replying to @roman01la @theKashey
vdom-diffing appears to be a deep-compare of the prev/current vdom, without structural sharing -- iterate through all children, stop only at shouldComponentUpdate
Reply Retweet Like
Matt Huebert Mar 28
Replying to @lucaongaro @dhh
Also holding on to my 2013. Only thing I don't like, it can't drive an external 4k without fans screeching. I bought an iMac to avoid the new laptops.
Reply Retweet Like
Matt Huebert retweeted
⸘Jack Rusher‽ Mar 26
ICYMI Here's an interactive webapp for tinkering with this generative system: ... and a locally runnable repo:
Reply Retweet Like
Matt Huebert Mar 26
Replying to @ralex1993
Would this also have been fixed by using functional updates with useState? I’d expect that to provide the same ordering as useReducer
Reply Retweet Like
Matt Huebert Mar 21
Hi Jacob, just saw your mention about sparkboard. happy to chat!
Reply Retweet Like
Matt Huebert retweeted
Thomas Ballinger Mar 20
This is the most impactful, influencing, and rewarding job I've ever had. Happy to chat about it. Although the job has changed a lot since I worked here, the incredibly high quality of the company and the community has not.
Reply Retweet Like
Matt Huebert retweeted
Szymon Kaliski Mar 20
Replying to @inkandswitch
I’ve been working with on various research projects for past few months, here’s the first article that I co-written on our end user programming experiments, check it out!
Reply Retweet Like
Matt Huebert Mar 19
Replying to @roman01la
am inquiring to see if we can learn something about reasoning behind leaving refs untouched during render phase,
Reply Retweet Like
Matt Huebert Mar 19
Replying to @roman01la @dan_abramov
i think the issue with immutable data structure comparison (whether via ClojureScript or a library like immutable.js) is inherently very broad - as general as "whenever dependencies are to be supplied to any hook"
Reply Retweet Like
Matt Huebert Mar 19
Replying to @roman01la
ie. it can be called 100 times and as long as the deps change once, the counter will increment, so behaviour should be as expected. but i'd like to be able to test this under whatever true "react concurrent" conditions are
Reply Retweet Like