| 3 | | Next, please consider using UTC times for all timestamps instead of localtimes. Foolscap is system for remote computation, and the remote end may or may not be in the same timezone as the local end, which may or may not be in the same timezone as the programmer who is looking at it. A nice, consistent simple way to deal with such things is just not worry as much about how sunny the sky was, and who was awake, in the land where the server lives and just use UTC for everything. |
| | 7 | Next, please consider using UTC times for all timestamps instead of |
| | 8 | localtimes. Foolscap is system for remote computation, and the remote end may |
| | 9 | or may not be in the same timezone as the local end, which may or may not be |
| | 10 | in the same timezone as the programmer who is looking at it. A nice, |
| | 11 | consistent simple way to deal with such things is just not worry as much |
| | 12 | about how sunny the sky was, and who was awake, in the land where the server |
| | 13 | lives and just use UTC for everything. |
| 5 | | (More seriously, the trade-off is cognitive difficulty of correlating events on a server from human-rhythm events that take place in the same timezone, such as meals and sleeping, vs. the cognitive difficulty of correlating events on a server with events on other computers. In my experience working in distributed systems, I'm more frequently interested in the latter correlations.) |
| | 15 | (More seriously, the trade-off is cognitive difficulty of correlating events |
| | 16 | on a server from human-rhythm events that take place in the same timezone, |
| | 17 | such as meals and sleeping, vs. the cognitive difficulty of correlating |
| | 18 | events on a server with events on other computers. In my experience working |
| | 19 | in distributed systems, I'm more frequently interested in the latter |
| | 20 | correlations.) |
