<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Date Formatting with YUI &#8211; Part III</title>
	<atom:link href="http://www.yuiblog.com/blog/index.php/2009/03/18/date-formatting-pt3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yuiblog.com/blog/2009/03/18/date-formatting-pt3/</link>
	<description>The official blog of the YUI Project.</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:46:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Philip Tellis</title>
		<link>http://www.yuiblog.com/blog/2009/03/18/date-formatting-pt3/comment-page-1/#comment-579129</link>
		<dc:creator>Philip Tellis</dc:creator>
		<pubDate>Thu, 19 Mar 2009 19:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/03/18/date-formatting-pt3/#comment-579129</guid>
		<description>Unix timestamps are in seconds, Javascript timestamps are in milliseconds.  What you&#039;re looking at in the example above are Javascript timestamps, ie, milliseconds.  To an experienced programmer dealing with timestamps in say PHP or C++, there will appear to be excess zeroes.  Three extra in fact.  I always feel a little uncomfortable when I look at it, but that&#039;s Javascript for you :) - at least there&#039;s no need for a separate HiResTime object.

The example&#039;s correct though.  Try it out.  There&#039;s a working link at the end of the post.</description>
		<content:encoded><![CDATA[<p>Unix timestamps are in seconds, Javascript timestamps are in milliseconds.  What you&#8217;re looking at in the example above are Javascript timestamps, ie, milliseconds.  To an experienced programmer dealing with timestamps in say PHP or C++, there will appear to be excess zeroes.  Three extra in fact.  I always feel a little uncomfortable when I look at it, but that&#8217;s Javascript for you :) &#8211; at least there&#8217;s no need for a separate HiResTime object.</p>
<p>The example&#8217;s correct though.  Try it out.  There&#8217;s a working link at the end of the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: poolboy</title>
		<link>http://www.yuiblog.com/blog/2009/03/18/date-formatting-pt3/comment-page-1/#comment-579056</link>
		<dc:creator>poolboy</dc:creator>
		<pubDate>Thu, 19 Mar 2009 02:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://yuiblog.com/blog/2009/03/18/date-formatting-pt3/#comment-579056</guid>
		<description>// Note: Unix timestamps output seconds since the Epoch,
    // so multiply by 1000 to get a JS timestamp


Whatever you&#039;ve got there aren&#039;t unix timestamps. There appear to be excess zeroes and you probably meant divide not multiply. Didn&#039;t bother to read the rest if the first 5 lines of example are so sloppy</description>
		<content:encoded><![CDATA[<p>// Note: Unix timestamps output seconds since the Epoch,<br />
    // so multiply by 1000 to get a JS timestamp</p>
<p>Whatever you&#8217;ve got there aren&#8217;t unix timestamps. There appear to be excess zeroes and you probably meant divide not multiply. Didn&#8217;t bother to read the rest if the first 5 lines of example are so sloppy</p>
]]></content:encoded>
	</item>
</channel>
</rss>

