4 ms·
> A sample of 20 APIs yielded nearly a 50/50 split. Is it still a 50/50 split today? I suspect ISO 8601 has grown to become the standard.
by divbzero 5y ago
> A sample of 20 APIs yielded nearly a 50/50 split.
Is it still a 50/50 split today? I suspect ISO 8601 has grown to become the standard.
- deleted 5y ago[deleted]
- hnbad 5y agoPublic APIs maybe. Internal? I'm not so sure. Since JSON doesn't have a time type, an ISO date field always requires validation and there are plenty of edge cases to consider (e.g. do you want to accept bare/naive datetimes, do you want to require all parts to be present, do you allow week dates, etc). The biggest advantage of ISO 8601 is probably that you can also use it to represent dates and/or times rather than only datetimes but this can result in unnecessary ambiguity (e.g. if you decide to split the datetime into a date and a time field and make assumptions about the timezone).