Reply to post: Re: It's 2022 and we're still coding dates as numbers (badly) or strings (worse)

Microsoft patches Y2K-like bug that borked on-prem Exchange Server

yetanotheraoc Silver badge

Re: It's 2022 and we're still coding dates as numbers (badly) or strings (worse)

"That would avoid all these shenanigans about trying to convert dates into numbers."

Everything in a computer is a sequence of 1s and 0s. Even your precious Objects are just a collection of numbers. Conversion will always be necessary, if not by you then by the library you call. "yyddmmssff" -.> int32 is an egregiously bad way to do it, but the solution is "library", not "objects".

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon