4 ms·
I would absolutely not use this for IT purposes if I could avoid it. The simple reason is that I have been bitten by time zone shenanigans way too often. The
by LordHeini 6y ago
I would absolutely not use this for IT purposes if I could avoid it.
The simple reason is that I have been bitten by time zone shenanigans way too often.
The same stands for databases always use timestamptz and not just timestamp.
Every frontend framework has functionality to properly and reliably format dates for a given locale.
As for filenames. It contains a space which is a pita for command line use.
- rob74 6y agoThis article is primarily about the date format, and that doesn't have anything to do with the timezone, so it's a bit unfair to hold time zone issues against it. Some issues are also self-made because people (including people who write libraries, frameworks etc.) choose to store a date (e.g. somebody's birthday) as a datetime...
- Grayskull 6y agoDate and time are separated by "T" and timezone is specifiable but optional. From wikipedia: "If a time zone designator is required, it follows the combined date and time. For example, "2007-04-05T14:30Z" or "2007-04-05T12:30−02:00"."
- trinix912 6y ago> As for filenames. It contains a space which is a pita for command line use. The biggest problem I see is the time notation part using colons. Windows still doesn't allow using them in filenames in most places.