News for hackers. Stuff that matters.
Re:Optimizing Python – A Case Study by pepijndevos on Friday May 29, 2015 @03:56AM (#9623288)
> Think for a second: time is only ever going to increase

Well, most of the time at least. Think about DST and leap seconds.

Re:Optimizing Python – A Case Study by ryan_sb on Friday May 29, 2015 @02:27PM (#9626400)
True, but in this particular case, the cost to time going (temporarily) backwards would only be connecting to a potentially-suboptimal disque node, and that would be remedied after the subjective-machine-time caught up with the previous subjective time.