Google Calander Date in iOS and default apps

[m0sher]

Hi,

While we wait to see if we are asked to participate I thought I’d start out by asking a couple questions iOS related.

Why doesn’t Calander show the date in the icon?

Can you make a setting that forces Siri to use Google Maps for directions, Keep for notes and chrome to be default?

 

[anon(10092459)]

Hi,

While we wait to see if we are asked to participate I thought I’d start out by asking a couple questions iOS related.

Why doesn’t Calander show the date in the icon?

Can you make a setting that forces Siri to use Google Maps for directions, Keep for notes and chrome to be default?

iOS is staunchly restrictive against third party apps for the most part. The date on the icon I'm sure needs access that iOS just doesn't allow.

Also, Siri will always default to Apple's apps. There is no way to change Siri to default to Google Maps, Keep or Chrome.

 

[anon(10388027)]

A more interesting computer, and Google calendar problem, is known as the 2038 calendar problem.

In fact, you can't go past December, 2036 on Google calendar.

Google is aware of the problem, and the answer, or solution, is all computer systems will have to be 64 bit systems... And that should not be a problem by 2038.

WIKI reference:

Google "Year 2038 Problem"

I tried pasting the link, but it won't let me.

 

[Rukbat]

and the answer, or solution, is all computer systems will have to be 64 bit systems

Not really - we were doing 64 bit arithmetic on 16 bit systems a long time ago - it's called multibyte precision arithmetic. (And it's actually quite trivial code.) The answer is a 64 bit "Unix date" (which can actually be done on a 4-bit computer - I just tried it on a simulator, to remind myself how to do multibyte - the code barely fit, but that's in a tiny little codespace). It's just this "we have to do it in one register" thinking that's causing a problem. We don't. I developed an accounting system back in 8 bit days that used 64 bit arithmetic about 10 years before IEEE 754 (it's not a big deal, programmatically).

But we know about it long in advance, we know the solution, so there isn't doing to be any "2038 panic", it will just be addressed by making the Unix date a 64 bit signed integer. And a lot of programs have already done that. (It wouldn't surprise me if Google Calendar changed in the next few years, with a modification totally invisible to users, except that they were getting an update to it.) That well take us past the Milky Way's collision with Andromeda.

https://en.wikipedia.org/wiki/Year_2038_problem is a pretty thorough look at the whole thing. (Don't know why you couldn't post a link - you have enough posts.)