Hexadecimal clock counting down to 2038 problem

Re:Hexadecimal clock counting down to 2038 problem by 29athrowaway on Sunday September 17, 2023 @02:30PM (#37547992)

Mainframe software will be the most painful to fix.

[ Parent | on HN ]

Re:Hexadecimal clock counting down to 2038 problem by ogogmad on Sunday September 17, 2023 @02:45PM (#37548135)

Obligatory: Could we use LLMs?

[ Parent | on HN ]

Re:Hexadecimal clock counting down to 2038 problem by tylerrobinson on Sunday September 17, 2023 @03:23PM (#37548453)

In case you missed it, that’s IBM’s plan (or at least their marketing team’s plan)!

https://arstechnica.com/information-technology/2023/08/ibms-...

[ Parent | on HN ]

Re:Hexadecimal clock counting down to 2038 problem by snickerbockers on Sunday September 17, 2023 @05:27PM (#37549523)

Also obligatory: calendar based cryptocurrency that measures time on the blockchain and also incidentally makes its creator rich by providing him with the largest initial allocation of currency.

[ Parent | on HN ]

Re:Hexadecimal clock counting down to 2038 problem by 29athrowaway on Monday September 18, 2023 @09:34PM (#37564669)

LLMs can suggest migrated code but you still have to review it and test it. And you have to review not only what it migrates but also what it does not.

So it does not save you much time.

[ Parent | on HN ]

Re:Hexadecimal clock counting down to 2038 problem by everythingctl on Sunday September 17, 2023 @07:43PM (#37550519)

Would any “real” mainframe software (not Linux on z) use Unix epoch dates though?

I’d have thought mainframe dates were mostly binary coded decimal in EBCDIC and already futureproofed during the y2k mania.

[ Parent | on HN ]