title: Getting moment.js moment 0 in unix timestamp
body: <p>I'm trying to use moment.js for similar calculations as python timedelta. </p>
  
  <p>what i have trouble with is this:</p>
  
  <pre><code>var d = moment(0);
  d
  Moment {_i: 0, _f: undefined, _l: undefined, _isUTC: false, _d: Thu Jan 01 1970 02:00:00 GMT+0200 (EET)…}
  _d: Thu Jan 01 1970 02:00:00 GMT+0200 (EET)
  _f: undefined
  _i: 0
  _isUTC: false
  _l: undefined
  __proto__: Object
  d.hours();
  2
  d.days();
  4
  </code></pre>
  
  <p>How can i get moment timestamp equal to unix timestamp 0, cause moment(0) does not seem to give me moment where days, hours, seconds and whatnot is all 0 and which transforms to unix timestamp 0 with moment.js format 'X' (<a href="http://momentjs.com/docs/#/displaying/format/" rel="noreferrer">link</a>)</p>
  
  <p>
  In response to comments:
  Usually timepickers work for picking time of certain date/day. And the value of timepicker 14:35 is usually interpreted as 14 hours and 35 minutes. You COULD use the same picker for letting user choose PERIOD (or timedelta) not TIME. Which would mean that there is 14 hours and 35 minutes between something, or something takes that time... so on...</p>
  
  <p>And you can use moment.js for simulating that functionality. Because:</p>
  
  <pre><code>moment(0).utc().hours == 0
  moment(0).utc().minutes == 0
  moment(0).utc().seconds == 0
  </code></pre>
  
  <p>You can just add (or let user add) hours, minutes, seconds to choose not time but PERIOD. Or timedelta. Unfortunatley this fails, when period is longer than 24 hours. because moment(0).utc().days() equals to 4 not 0.</p>
  
  <p>Not sure why this WHY is relevant, when for all reasons i can think of moment(0).utc().days() should be 0 not 4...
  </p>