Brian Vaughn

I decided to go for it thoughI got a screw driver and moved the G saddle forward a bit to compensate for the new string– and it plays perfectly now! I'm pretty thrilled by this outcome. It was a learning experience for me, and it turned out to be successful.

Unfortunately it messed up the intonation but I did a bit of reading and learned that it was to be expected. My best options seemed to be to use a heavier gauge wound G, or to tweak the setup a bit myself (something I was pretty hesitant to do– since my 060 plays so well).

I recently replaced the unwound G on my 6-string electric with a wound G. (I've always disliked the sound of the unwound G on electrics, but it didn't occur to me that I could just replace it until recently.) I liked the sound of the G much better after replacing it– BUT–

Clocked another 5 minute mile today! 173bpm pulse

I decided against adding a spreadStyleProps property for now because of Flow type complications (which seemed like an indication that the pattern might not be a great one to begin with). I will likely revisit this decision before a v2 release.

Twitter has been pretty quiet this week and I've enjoyed a break from tech "drama" I encourage everyone to take another week of PTO I'm not ready yet for it to resume

I've seen a few new year's resolution tweets to use Twitter less often

All three of these can be thought of as advanced optimizations. None are required for typical react-window usage, but I wanted to better support use cases that require more fine tuning.

Super Smash Brothers takes more skill than being a software developer I've spent years becoming passably decent at one. I'm not sure I have enough life left to master the other.

I might also be able to do a release that adds an opt-in API for individual style props, and logs a DEV deprecation warning for the old style object prop. This would give people a heads up to gradually migrate to the new API. Could probably even write a codemod for it.

I kind of lean toward option two, even though it would be a breaking change and so require a major release. I could export a helper function that can be used to create the proper default style object, but leave it up to users to decide between absolute position, translate, etc

This means that on the next scroll event, all items will re-render because of the new wrapper object. Some possible ideas to deal with this: 1. Export a custom sCU that knows to compare style object props 2. Pass top/left/width/height as top-level props and defer style creation

react-window passes item renderers a style object containing top, left, width, height, (and position) values. I cache these objects while scrolling to avoid unnecessarily re-rendering items during perf sensitive times, but I clear the cache afterward to avoid stale cached styles–

Be kind to each other It might feel satisfying to leave an angry GitHub comment, but they often cause real stress and hurt for maintainers– even ones you might think are too big or successful to be affected by it.