title: What happens after 2038-1-19?
body: <p>Starting with the epoch time </p>
  
  <blockquote>
    <p>1 January 1970 00:00:00</p>
  </blockquote>
  
  <p>and counting to the limit a 32-bit signed integer can reach, the day when we reach the limit of counting time (in computer, of course) is 2038-1-19, as given in the <a href="https://stackoverflow.com/questions/1090869/why-is-1-1-1970-the-epoch-time">answer</a> by Matt Howells.</p>
  
  <blockquote>
    <p>a 32-bit signed integer using 1970-1-1 as its epoch can represent dates up to 2038-1-19, on which date it will wrap around to 1901-12-13</p>
  </blockquote>
  
  <p>If it wraps around to a back date, what then is the solution to count the time forward instead of wrapping to back date? As given in <a href="http://en.wikipedia.org/wiki/Year_2038_problem" rel="nofollow noreferrer">wikipedia</a></p>
  
  <blockquote>
    <p>There is no universal solution for the Year 2038 problem.</p>
  </blockquote>
  
  <p>I don't feel comfortable about this! There must be some thought as to the solution to this problem. I understand the cause for not using a 64-bit integer in the first place (which would give us 292 billion years to relax!): not many machines could (could any?) handle 64-bit integers that time. And switching to a 64-bit integer <em>now</em> has its own problems. What then could be the solution to this?</p>