Separate names with a comma.
Discussion in 'iOS 7' started by FatPuppy, Dec 16, 2013.
I mean... in this screenshoot it is year 69 B.C.
Because why not? It wouldn't take much effort and it doesn't affect anything.
Exactly. There's no reason not to.
Because I need to book a hotel room for NYE 2999.
Yeah but... 69 B.C. ??? Really?
Apple didn't add anything. Obviously the calendar app can calculate and display any year you ask it to show. It's a simple algorithm that generates the result.
You have a lot of free time, don't you ?
i kept scrolling up and the calendar stops at 4716 BC. Kind of a weird year to pick. If it is an algorithm it should go back indefinitely.
Unfortunately it can't be totally accurate going back that far. The switch over from Julian Calendar to Gregorian Calendar took about 350 years. Going back that far to see what day of the week something happened centuries ago won't be correct.
Who cares????, no one is ever gonna use a calendar that far.
There is no December in 69 BC and February had 31 days? January has 28?
In case you take your iPad back in time
Holy mother of gawd! Thank you so much! I'm making an app and the calendar was gonna drive me insane!! Didn't think of any other way to do it other than make layouts for every month of every year. (Sounds really stupid now actually)
This will help you.
I'll take a look at it. The app is for the Android Market but it might give insight. Thanks!
I can only think if someone wanted to know what day of the week something happened.
Correct. Even Time Lords need smartphones, and this just sends a whole lot of business Android's way.
Exactly! All this iWatch talk, and nobody figured out the big plan...
It will be correct according to Gregorian standards. You could use a Julian calendar for the modern times if you wanted to. Dates might not line up with what everyone else uses, but it would technically be correct according to the calendar you're using. Really no different than kilograms vs pounds, Celsius vs Fahrenheit, etc.
Anyways, it's not like Apple developers had to write code for each year. The algorithm is relatively simple, so calendars for any year can be generated on the fly.
If I had to guess, the limit is likely due to the length of an int or something. Similar to the Year 2038 problem just in the other direction. Or 4, 7, 1 and 6 were some developer's lucky numbers in the fortune cookie they got when they went out to lunch.
Or the developer's a young earth creationist
Never knew it went back that far. You learn something new everyday.
Isn't that roughly the time some believe God created everything? There are those who argue the world is 6000 years old, apple may agree.....?