A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.
A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.
Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
Speed, on the full configs: 3.6–5.7x faster on one thread, up to 38x on 16, and 37–400 MB of memory instead of 3–4 GB. A single file takes about 10 ms, which is the number I actually cared about, because that’s what makes it usable in a pre-commit hook.
Speed, on the full configs: 3.6–5.7x faster on one thread, up to 38x on 16, and 37–400 MB of memory instead of 3–4 GB. A single file takes about 10 ms, which is the number I actually cared about, because that’s what makes it usable in a pre-commit hook.