3 ms·

I do like how this seems to stop curiously short of 2038.

• sockaddr 3y ago
  This was my first thought too
• throw0101d 3y ago
  Per the official support document: > Sustaining Support Ends: Indefinite * https://www.oracle.com/us/assets/lifetime-support-hardware-301321.pdf https://www.oracle.com/us/assets/lifetime-support-hardware-3... If you're willing to cut a chequing, they're willing to sell you a support contract. Solaris has supported a 64-bit time_t since (at least) 2010: > The 64-bit system interfaces are inherently more capable than some of their 32-bit equivalents. Application programmers concerned about year 2038 problems (when 32-bit time_t runs out of time) can use the 64-bit time_t. While 2038 seems a long way off, applications that do computations concerning future events, such as mortgages, might require the expanded time capability. * https://docs.oracle.com/cd/E19455-01/806-0477/6j9r2e2ah/index.html https://docs.oracle.com/cd/E19455-01/806-0477/6j9r2e2ah/inde...
  • snvzz 3y ago
    can vs must, or even should. 2038 will be a problem, because using 64 bit time was optional. Binary compatibility was kept, but 2038 will have some chaos, and Oracle won't care because support will have already ended.
    • justinclift 3y ago
      > support will have already ended. But the support is "indefinite", meaning it doesn't haven't an end date for the customers on that tier.