5 ms·
Working with time is full of pitfalls, especially around clock monotonicity and clock synchronisation. I wrote an article about some of those pitfalls some time
by SerCe 2y ago
Working with time is full of pitfalls, especially around clock monotonicity and clock synchronisation. I wrote an article about some of those pitfalls some time ago [1]. Then, you add time zones to it, and you get a real minefield.
[1]: https://serce.me/posts/16-05-2019-the-matter-of-time https://serce.me/posts/16-05-2019-the-matter-of-time
- mmooss 2y agoYou are a developer who works with time and you named your file, "16-05-2019-the-matter-of-time"? :)
- eru 2y agoWhat's wrong with that?
- lysium 2y agoThat’s not a standard format. ISO format is yyyy-mm—dd. Also, sorts nicely by time if you sort alphabetically.
- eru 2y agoYes, I know. But for your personal file names, you can pick whatever you feel like.
- BrandoElFollito 2y agoThey wrote it on the 16th of May, or the 5th of Bdrfln, we will never know.
- eru 2y agoPerhaps it's just named for that date, and not written then? In any case, dates only have to make sense in the context they are used. Eg we don't know from just the string of numbers whether it's Gregorian, Julian, or Buddhist or Japanese etc calendar.
- BrandoElFollito 2y agoWho know, it may not even be a date? But seriously, https://xkcd.com/1179/ https://xkcd.com/1179/
- gsich 2y agoAssuming Gregorian is a sane choice.
- eru 2y agoNot any worse than most other commonly used calendars, and it's got the benefit of network effects: many people use it, and virtually everyone will be at least somewhat familiar with it.
- SerCe 2y agoYeah, sorry mate, it can be confusing, will use unix epoch next time.
- deleted 2y ago[deleted]