Pieter De Baets

As apparently sht.tl is down, I think having a way to use an alternative shortener has its merits...

I think this is a great overview of how we can incrementally move RN closer to web standards and reduce API fragmentation. When it comes to implementing this though, let's...

Please provide a unit tests that shows how this behaviour was broken before and how this change resolves it. This will help me understand the goal here and prevent us...

Does this correctly handle scenarios like this? ``` style={[ {backgroundColor: animatedValue}, {backgroundColor: 'red'}, ]} ``` The expected outcome would be that `animatedValue` is not used.

UIViewController used to remove UIViews that were not being used, but that was dropped in iOS6 since it didn't provide a lot of memory benefits. For RN though, every view...

Alternatively, could we use `shouldComponentUpdate` to turn off reconciliation for invisible parts of the navigation stack?

Thanks for the fix. The approach makes sense, but I'd cautious this may cause performance regressions, given the existing fast path that exists in JSC for all-ASCII stings. I'd also...

Could this be due to https://github.com/facebook/react-native/commit/d8c25ca1b62df2b93f70bbb1f7b379643ab9ccd4? Could you try backing it out to validate?

#34927 attempts to resolve this issue by enabling the new behaviour only on Fabric. I verified this resolves the repro given here, but would appreciate help testing other scenarios too...

Does this apply to RN latest? We've landed https://github.com/facebook/react-native/commit/5cdf3cf72613a2068884151efb08fd4c17fec5fd last month which switches out the implementation of Animated to be concurrent-safe and may have different behaviour.