Josh Ribakoff

I subscribed. I'd love to help with it / try it out @cartant

Note that NTP times are subject to clock slew and adjustments by NTP, and subject to error due to NTP mis configurations or peering issues, and subject to time drift...

> o calculate RTT we use RTCP RR, I would say the above is incorrect (if you want the actual delay of the media), because in creating local simulations &...

One other use case we want to call out is consider that we start a transition to fetch data and render our chart (useTransition), and it takes a long time...

Yeah same issue as https://github.com/remix-run/react-router/issues/7460

I think the solution is to remove the overzealous check navigating isn’t a layout effect (depending on your use case), and normal effects don’t run in the render phase, so...

Both a 0ms timeout and 1ms can take longer than 1ms, the 2nd argument passed to setTimeout is just a minimum delay. The aforementioned testing utilities (waitFor) are capable of...

No I am already using memoization. I don’t think memoization affects anything about the point in time which the function gets called. It still runs synchronously inside of the child...

😆 @ryanflorence this is not resolved 🤷🏻‍♂️

To be clear, this is not a PHP bug. PHP can preserve my data just fine. ``` php $str = "{foo:[], bar:{}}"; var_dump(json_encode(json_decode($str)) === $str); // true ``` json_decode() works...