Hacker News new | past | comments | ask | show | jobs | submit login

"Zero and negative dates are not valid, so the earliest instant in time that can be represented as a timestamp is Jan 01, 0001"

That seems to be...a problem? How do you deal with archeological dates, of which there are many, in Ion?




That’s an interesting question. On the one hand, it feels weird that you can’t represent those dates at all.

On the other hand, representability of a given date becomes progressively less useful the further back in time you go, and stuff becomes really gnarly once you go past the Julian calendar in 45BC.

Also, simplifying to “no dates before Jan 1 0001” has very little impact on applications dealing with the modern-ish world (with “modern” generously defined as “anything after the collapse of the Roman Empire”), and I can only assume applications dealing with earlier times could do with a more specialised representation for dates anyway.


Just to give one example, in Thailand right now it's the year 2564.

1 BC for some is not "-1" for everyone.


What modern tech service (of the kind that would have use for Ion) is dealing with archaeological dates _at scale_? Honest question.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: