gerges

dev, perf @ 🤖 (formerly slack, trello, atlassian, invision)

[gerges @gerges]

@marcosscriven @brownbagcrisps I think the most GF labeling requirements are under 20ppm, which I believe is the intersection of "probably safe", "easy to test for" and "achievable for manufactures"

[gerges @gerges]

@potetotes 👀 I may try this shimmed one you added to bluesky since react@19 is likely >6mo out for us. 🙏🏽

https://t.co/vq4QDf9qX4

[gerges @gerges]

@acdlite @en_JS @_gsathya Really exciting! Reach out if y'all are looking for pilots. Assuming there aren't too many pre reqs, we have the infra to a/b this and see impact on long tasks/input delay/redux subscriber notification timings/etc

[gerges @gerges]

@alextabor95 @jjasmineimanii @Allegiant Yeah. We were waiting on these planes from Knoxville. So glad the only flight Allegiant could offer me was a week from today. Just lost $1500 to Delta

[gerges @gerges]

@brian_d_vaughn can open something on gh instead, this just felt more like a question than a bug

[gerges @gerges]

@brian_d_vaughn I noticed react-virtualized-auto-sizer diverged from whats in react-virtualized itself (ex ResizeObserver support). Was this intentional? Would I be good to use the extracted one with `react-virtualized`?

[gerges @gerges]

@acemarke @replayio I think with a profiling build like this, and with the profiling build of react you could build a pretty compelling redux perf devtools with profile recording and perf insights around selectors / reducers / etc

[gerges @gerges]

@acemarke @replayio I've considered

- Injecting <Profiler>'s to get react time of with connected component updating
- A babel transfor for selectors to better understand self/total time (subselectors)
- Stability checks
- Identifying memo candidates by understanding selector deps and their change

[gerges @gerges]

@trunarla I use a Kasa smart plug 🔌, for only $20 you can stop the thread altogether without all that annoying fan noise

[gerges @gerges]

@JuntaoQiu This is a sparse array, so the first 10 values are not actually undefined (although they'll come out as undefined in some cases). Ex: Array.prototype.forEach will only invoke your callback once, vs 11 times if it truly was filled with undefined

[gerges @gerges]

@malchata @hi__mayank Could also cover why drawing boxes around things (ex: shadow dom) lets the browser skip work. I think the mob can be quelled by flat out acknowledging that these are advanced problems and optimization here isn't always necessary or worthwhile

[gerges @gerges]

@malchata @hi__mayank IMO rendering is the big marble machine that we like to assume is never a bottleneck. Would love something official. Highlight some of misunderstandings/de-opts. style/layout/paint (tiling), compositor, raster (even skia+gpu). Some DOM based drawing could make for good examples.

[gerges @gerges]

@scinos Its my day to return the favor @scinos!

[gerges @gerges]

@slightlylate 🌶 spicy. i'm getting lockscreen vibes.

[gerges @gerges]

@slightlylate For performance sensitive apps I might even add unnecessary compositing to this list. It's unfortunate that you basically need to write a layout+rendering engine to understand why.

[gerges @gerges]

@slightlylate IMO this lands in the ocean of "the life of a pixel" and outside Chromium traces can be opaque/unapproachable. I always felt a Chromium engineer could pretty quickly look at css-in-js and say "oh no don't do THAT". Better tooling/insight here would be awesome.