> 4.Item 4, changed.

I believe this was where Khaled fixed the bugs where scripts would register as having changed after daylight savings. There were inconsistencies between API calls, and I think Khaled did a unification to iron those issues out. I don't think CTIME (unix time) as a 32 or 64 bit number format is related to this.

I don't know that UNIX time has taken an official update to address the Y2k38 bug. https://en.wikipedia.org/wiki/Year_2038_problem

What would you do with microseconds in such a spongy scripting language? Except to manage file modified/creation dates-time values.

I would like to see a CTIME/ASCTIME that handles system clock milliseconds (only to system clock's resolution, ie, 64 or 100 Hz).

Well. At least I won lunch.
Good philosophy, see good in bad, I like!