The language is rooted in the same logic as people. Your first year was between the ages of 0 and 1. The first year before you were born is between -1 and 0. There is no 0th year because 0 is a point in time and not a range in time.
Your explanation works equally well for any integer though. You could say the same of 1.
I think you’re saying that it’s a fencepost issue. But even for personal ages this doesn’t check out: for a year after you are born, your age is “0.” A one-year-old baby is in the following year.
I feel you’ve missed the point I was making and assumed I’ve made another. Age number and year number are different. You’re in your first year when your age is not yet 1. You’re in your second year when your age is between 1 and 2.
Years follow numbers as in "this year was the first/second/third year of ", not “this year was the year turned X years old”
Oh I see. Sure, historically it makes sense that years have been ordinal numbers. But in the modern era with all our math and computational knowledge, it is not convenient anymore. It means off-by-one errors are easy to commit when comparing BC and AD years.
This is why programming languages all index from 0 rather than 1 (knuth and lua be damned)
Absolute value. Both systems count time from the same epoch, or zero point.
One year before the epoch is 1 January 1BCE One year after the epoch is 31 December, 1CE.
Half a year before the epoch (-0.5 years) is June 30, 1BCE. Half a year after the epoch (0.5 years) is July 1st, 1CE. These dates occur within the first year before the epoch, and the first year after the epoch, respectively.
This explanation is unclear to me. Why do we choose the later of the two endpoints of the year for (0, 1) but the earlier of the two for (-1, 0)?
The language is rooted in the same logic as people. Your first year was between the ages of 0 and 1. The first year before you were born is between -1 and 0. There is no 0th year because 0 is a point in time and not a range in time.
Your explanation works equally well for any integer though. You could say the same of 1.
I think you’re saying that it’s a fencepost issue. But even for personal ages this doesn’t check out: for a year after you are born, your age is “0.” A one-year-old baby is in the following year.
I feel you’ve missed the point I was making and assumed I’ve made another. Age number and year number are different. You’re in your first year when your age is not yet 1. You’re in your second year when your age is between 1 and 2.
Years follow numbers as in "this year was the first/second/third year of ", not “this year was the year turned X years old”
Oh I see. Sure, historically it makes sense that years have been ordinal numbers. But in the modern era with all our math and computational knowledge, it is not convenient anymore. It means off-by-one errors are easy to commit when comparing BC and AD years.
This is why programming languages all index from 0 rather than 1 (knuth and lua be damned)
Because until the Middle Ages, Europeans were afraid of the number 0.
Absolute value. Both systems count time from the same epoch, or zero point.
One year before the epoch is 1 January 1BCE One year after the epoch is 31 December, 1CE.
Half a year before the epoch (-0.5 years) is June 30, 1BCE. Half a year after the epoch (0.5 years) is July 1st, 1CE. These dates occur within the first year before the epoch, and the first year after the epoch, respectively.
For the same reason why 1.5 is on the right from 1 but -1.5 is on the left from -1