<?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: Epoch win!</title>
	<atom:link href="http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/</link>
	<description>I am an astronomer, writer, and skeptic. I likes reality the way it is, and I aims to keep it that way. My real name is Phil Plait, and I run the Bad Astronomy blog.</description>
	<lastBuildDate>Tue, 14 Feb 2012 08:00:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: JB</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-329395</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Sun, 07 Nov 2010 00:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-329395</guid>
		<description>Epoch? I was hoping for amusing at the very least. Dorky? OK you got me! I&#039;ll see if I can cook up something more amusing. I&#039;m guessing you are only in your twenties. I&#039;m in my fifties..., all I have to do is dust off some of my time tested jokes.

Maybe say something in programming. I&#039;ll make it easy, I&#039;ll use Cobol 77.  I really appreciate the nomination, however, it seems that there are more prospective candidates on your end. I&#039;m here by myself. I need reinforcements.

I&#039;ll keep an eye on you to see how you perform online. Oh, thanks for the compliment.

jeff</description>
		<content:encoded><![CDATA[<p>Epoch? I was hoping for amusing at the very least. Dorky? OK you got me! I&#8217;ll see if I can cook up something more amusing. I&#8217;m guessing you are only in your twenties. I&#8217;m in my fifties&#8230;, all I have to do is dust off some of my time tested jokes.</p>
<p>Maybe say something in programming. I&#8217;ll make it easy, I&#8217;ll use Cobol 77.  I really appreciate the nomination, however, it seems that there are more prospective candidates on your end. I&#8217;m here by myself. I need reinforcements.</p>
<p>I&#8217;ll keep an eye on you to see how you perform online. Oh, thanks for the compliment.</p>
<p>jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-156031</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Sat, 14 Feb 2009 21:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-156031</guid>
		<description>I have a mac, I put that into the terminal and got a syntax error, wtf is up with that?</description>
		<content:encoded><![CDATA[<p>I have a mac, I put that into the terminal and got a syntax error, wtf is up with that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BethK</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-156030</link>
		<dc:creator>BethK</dc:creator>
		<pubDate>Sat, 14 Feb 2009 20:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-156030</guid>
		<description>Low tech geeks remember that March 14 is pi day with 1:59 adding more precision and then 26 seconds for even more. Aside: I just learned that my 13yo son knows pi to 30 digits.

And my 15yo daughter already knew about the 1234567890 date thing. 

Where did I go right in raising them?</description>
		<content:encoded><![CDATA[<p>Low tech geeks remember that March 14 is pi day with 1:59 adding more precision and then 26 seconds for even more. Aside: I just learned that my 13yo son knows pi to 30 digits.</p>
<p>And my 15yo daughter already knew about the 1234567890 date thing. </p>
<p>Where did I go right in raising them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John B. Sandlin</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-156024</link>
		<dc:creator>John B. Sandlin</dc:creator>
		<pubDate>Sat, 14 Feb 2009 19:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-156024</guid>
		<description>I get the Unix time gag.  I&#039;m not geek enough to have run the math and remembered it.  I didn&#039;t feel too bad about that... but the Crab reference got me...

10:54 for the Crab?  I had to look up the Crab.  

Star Chart gave me: 
    NGC 1952 / M1 / The Crab Nebula - RA 05h 34m 31.97s / Dec. +22° 00′ 52.1″...

Then I looked it up in Wiki....

Oh!  That&#039;s when it went KerPow (well, the year was 1054... I don&#039;t know what time of day...)

I feel bad for not getting that without looking it up.

jbs</description>
		<content:encoded><![CDATA[<p>I get the Unix time gag.  I&#8217;m not geek enough to have run the math and remembered it.  I didn&#8217;t feel too bad about that&#8230; but the Crab reference got me&#8230;</p>
<p>10:54 for the Crab?  I had to look up the Crab.  </p>
<p>Star Chart gave me:<br />
    NGC 1952 / M1 / The Crab Nebula &#8211; RA 05h 34m 31.97s / Dec. +22° 00′ 52.1″&#8230;</p>
<p>Then I looked it up in Wiki&#8230;.</p>
<p>Oh!  That&#8217;s when it went KerPow (well, the year was 1054&#8230; I don&#8217;t know what time of day&#8230;)</p>
<p>I feel bad for not getting that without looking it up.</p>
<p>jbs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheBlackCat</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-156003</link>
		<dc:creator>TheBlackCat</dc:creator>
		<pubDate>Sat, 14 Feb 2009 16:27:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-156003</guid>
		<description>@ Kid: Bah, geeks don&#039;t car about odd numbers.  Odd an even are simply a result of our arbitrary obsession with the number 2.  If we had trilateral symmetry it would probably be looking for numbers that are divisible by 3.  &lt;i&gt;Real&lt;/i&gt; geeks are waiting until 2/2/2011, the next all-prime date.</description>
		<content:encoded><![CDATA[<p>@ Kid: Bah, geeks don&#8217;t car about odd numbers.  Odd an even are simply a result of our arbitrary obsession with the number 2.  If we had trilateral symmetry it would probably be looking for numbers that are divisible by 3.  <i>Real</i> geeks are waiting until 2/2/2011, the next all-prime date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kid Cool</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-156002</link>
		<dc:creator>Kid Cool</dc:creator>
		<pubDate>Sat, 14 Feb 2009 16:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-156002</guid>
		<description>I surprised at all the geeks here not mentioning 11/19/1999 being the last all odd number date until 11/11/3111. Maybe 01/01/3111, but do the 0&#039;s count?

How about 02/02/2000 the first all even number date since 8/28/888</description>
		<content:encoded><![CDATA[<p>I surprised at all the geeks here not mentioning 11/19/1999 being the last all odd number date until 11/11/3111. Maybe 01/01/3111, but do the 0&#8242;s count?</p>
<p>How about 02/02/2000 the first all even number date since 8/28/888</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ProofByInduction</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155993</link>
		<dc:creator>ProofByInduction</dc:creator>
		<pubDate>Sat, 14 Feb 2009 15:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155993</guid>
		<description>&quot;If you thought you could outdork me, give up now.&quot;

Phil, most of the above entries leave you in the dust as to dorkiness....:-)</description>
		<content:encoded><![CDATA[<p>&#8220;If you thought you could outdork me, give up now.&#8221;</p>
<p>Phil, most of the above entries leave you in the dust as to dorkiness&#8230;.:-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cardoso</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155983</link>
		<dc:creator>cardoso</dc:creator>
		<pubDate>Sat, 14 Feb 2009 13:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155983</guid>
		<description>Don&#039;t forget the 17:01, Trek Hour.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t forget the 17:01, Trek Hour.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MadScientist</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155974</link>
		<dc:creator>MadScientist</dc:creator>
		<pubDate>Sat, 14 Feb 2009 11:02:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155974</guid>
		<description>@Mike:

  I don&#039;t know why you say my system isn&#039;t POSIX compliant (I haven&#039;t checked the latest POSIX spec or proposals).

@Caleb:

 64 bit could be the problem; I tried using GNU &#039;date&#039; as blf suggested and I still get the naively expected time rather than the time warp.  I&#039;ve got a &#039;pure&#039; 64-bit system on an AMD Opteron.  So is it my kernel, the GNU libraries, or both.  Now I don&#039;t even know if it&#039;s just Perl or something else in my system.  Oh well, it&#039;s not something I need to worry about at the moment. :)</description>
		<content:encoded><![CDATA[<p>@Mike:</p>
<p>  I don&#8217;t know why you say my system isn&#8217;t POSIX compliant (I haven&#8217;t checked the latest POSIX spec or proposals).</p>
<p>@Caleb:</p>
<p> 64 bit could be the problem; I tried using GNU &#8216;date&#8217; as blf suggested and I still get the naively expected time rather than the time warp.  I&#8217;ve got a &#8216;pure&#8217; 64-bit system on an AMD Opteron.  So is it my kernel, the GNU libraries, or both.  Now I don&#8217;t even know if it&#8217;s just Perl or something else in my system.  Oh well, it&#8217;s not something I need to worry about at the moment. <img src='http://blogs.discovermagazine.com/badastronomy/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James McCann</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155972</link>
		<dc:creator>James McCann</dc:creator>
		<pubDate>Sat, 14 Feb 2009 10:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155972</guid>
		<description>Replacing the characters you typed with different characters - with features like that who needs bugs?

gawk -- &#039;BEGIN { print strftime(&quot;%c&quot;, ARGV[1]) }&#039; 1234567890

gives the inverse of date +%s</description>
		<content:encoded><![CDATA[<p>Replacing the characters you typed with different characters &#8211; with features like that who needs bugs?</p>
<p>gawk &#8212; &#8216;BEGIN { print strftime(&#8220;%c&#8221;, ARGV[1]) }&#8217; 1234567890</p>
<p>gives the inverse of date +%s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Perl Guy</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155971</link>
		<dc:creator>Perl Guy</dc:creator>
		<pubDate>Sat, 14 Feb 2009 10:28:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155971</guid>
		<description>It should read:

perl -e &#039;print scalar localtime(1234567890) . &quot;\n&quot;;&#039;

Replace the , with a . and change the open/close single quotes with apostrophes.

And DAMN Phil, you should have left it in on thursday. I missed it on Friday.</description>
		<content:encoded><![CDATA[<p>It should read:</p>
<p>perl -e &#8216;print scalar localtime(1234567890) . &#8220;\n&#8221;;&#8217;</p>
<p>Replace the , with a . and change the open/close single quotes with apostrophes.</p>
<p>And DAMN Phil, you should have left it in on thursday. I missed it on Friday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blf</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155964</link>
		<dc:creator>blf</dc:creator>
		<pubDate>Sat, 14 Feb 2009 09:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155964</guid>
		<description>Using GNU date(1), date --date=@1234567890 will also print the time; add --utc if you want it in UTC; or export an appropriate TZ.  No reason to use perl(1) at all.

For those of you arguing about 32-bitness, whether or not time_t is unsigned, etc., the Rationale in the &lt;EM&gt;original&lt;/EM&gt; (IEEE) POSIX.1-1988 standard contained a fairly lengthy discussion of the entire subject.</description>
		<content:encoded><![CDATA[<p>Using GNU date(1), date &#8211;date=@1234567890 will also print the time; add &#8211;utc if you want it in UTC; or export an appropriate TZ.  No reason to use perl(1) at all.</p>
<p>For those of you arguing about 32-bitness, whether or not time_t is unsigned, etc., the Rationale in the <em>original</em> (IEEE) POSIX.1-1988 standard contained a fairly lengthy discussion of the entire subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: freespace</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155957</link>
		<dc:creator>freespace</dc:creator>
		<pubDate>Sat, 14 Feb 2009 06:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155957</guid>
		<description>Ah, good pick up. I think my poor 32bit processor overflowed... the 11 digit pi I used is ~31x larger than the largest unsigned 32bit int can hold...

So some one on a 64bit system can try it and let us know :P</description>
		<content:encoded><![CDATA[<p>Ah, good pick up. I think my poor 32bit processor overflowed&#8230; the 11 digit pi I used is ~31x larger than the largest unsigned 32bit int can hold&#8230;</p>
<p>So some one on a 64bit system can try it and let us know <img src='http://blogs.discovermagazine.com/badastronomy/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Weiss</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155956</link>
		<dc:creator>John Weiss</dc:creator>
		<pubDate>Sat, 14 Feb 2009 05:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155956</guid>
		<description>Freespace?  Shouldn&#039;t pi-time be in like 60 years?  It&#039;s taken nearly 30 to get to 1.2x10^10 seconds, shouldn&#039;t it take nearly twice that to cover another 2x10^10?

(Also, you have 11 digits, there.  That&#039;ll be... 1000 years?)</description>
		<content:encoded><![CDATA[<p>Freespace?  Shouldn&#8217;t pi-time be in like 60 years?  It&#8217;s taken nearly 30 to get to 1.2&#215;10^10 seconds, shouldn&#8217;t it take nearly twice that to cover another 2&#215;10^10?</p>
<p>(Also, you have 11 digits, there.  That&#8217;ll be&#8230; 1000 years?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: freespace</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155953</link>
		<dc:creator>freespace</dc:creator>
		<pubDate>Sat, 14 Feb 2009 05:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155953</guid>
		<description>date -u will output in UTC time too.</description>
		<content:encoded><![CDATA[<p>date -u will output in UTC time too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: freespace</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155952</link>
		<dc:creator>freespace</dc:creator>
		<pubDate>Sat, 14 Feb 2009 05:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155952</guid>
		<description>Extra dorky, pi time:

date -r 31415926535
Thu 25 Oct 2012 19:57:43 EST</description>
		<content:encoded><![CDATA[<p>Extra dorky, pi time:</p>
<p>date -r 31415926535<br />
Thu 25 Oct 2012 19:57:43 EST</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. ALan Zoppa</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-2/#comment-155947</link>
		<dc:creator>C. ALan Zoppa</dc:creator>
		<pubDate>Sat, 14 Feb 2009 03:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155947</guid>
		<description>Phil, FYI---


date +%s

will do the trick</description>
		<content:encoded><![CDATA[<p>Phil, FYI&#8212;</p>
<p>date +%s</p>
<p>will do the trick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Chemist</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155924</link>
		<dc:creator>The Chemist</dc:creator>
		<pubDate>Sat, 14 Feb 2009 00:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155924</guid>
		<description>Must make it to my Linux box before midnight.</description>
		<content:encoded><![CDATA[<p>Must make it to my Linux box before midnight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harold</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155915</link>
		<dc:creator>Harold</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155915</guid>
		<description>Oh. Just sounded it out. Never mind.</description>
		<content:encoded><![CDATA[<p>Oh. Just sounded it out. Never mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harold</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155914</link>
		<dc:creator>Harold</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155914</guid>
		<description>OK, now I&#039;m confused about the &quot;comb jelly time&quot; comment.</description>
		<content:encoded><![CDATA[<p>OK, now I&#8217;m confused about the &#8220;comb jelly time&#8221; comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy from Boulder</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155909</link>
		<dc:creator>Timothy from Boulder</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155909</guid>
		<description>The Google logo this afternoon commemorates nerddom.</description>
		<content:encoded><![CDATA[<p>The Google logo this afternoon commemorates nerddom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lagomorph</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155907</link>
		<dc:creator>lagomorph</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155907</guid>
		<description>No worries.  I guess it comes down to the definition of UNIX.  I&#039;m fairly minimalist.  To me, OpenBSD simply shares my &lt;a href=&quot;http://openbsd.org/goals.html&quot; rel=&quot;nofollow&quot;&gt;goals&lt;/a&gt;.  They adhere to standards when they make sense.  They put files where they belong.  They care about quality and correctness and tight code.  I associate this with true, traditional UNIX.  OS-X is not typically used in any way that would feel like UNIX in a traditional sense.  When you probe under the hood, in my opinion, the part that is UNIX-like is a mess.  It&#039;s UNIX with a whole bunch of stuff grafted on and that &quot;stuff&quot; is pretty much what most users are going to interact with.  It can look pretty slick on the outside though.</description>
		<content:encoded><![CDATA[<p>No worries.  I guess it comes down to the definition of UNIX.  I&#8217;m fairly minimalist.  To me, OpenBSD simply shares my <a href="http://openbsd.org/goals.html" rel="nofollow">goals</a>.  They adhere to standards when they make sense.  They put files where they belong.  They care about quality and correctness and tight code.  I associate this with true, traditional UNIX.  OS-X is not typically used in any way that would feel like UNIX in a traditional sense.  When you probe under the hood, in my opinion, the part that is UNIX-like is a mess.  It&#8217;s UNIX with a whole bunch of stuff grafted on and that &#8220;stuff&#8221; is pretty much what most users are going to interact with.  It can look pretty slick on the outside though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caleb</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155906</link>
		<dc:creator>Caleb</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155906</guid>
		<description>There it goes!

http://coolepochcountdown.com/</description>
		<content:encoded><![CDATA[<p>There it goes!</p>
<p><a href="http://coolepochcountdown.com/" rel="nofollow">http://coolepochcountdown.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cusp</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155903</link>
		<dc:creator>Cusp</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155903</guid>
		<description>&gt;&gt; If you have a Mac or Unix machine

Modern macs are unix (for small values of unix)</description>
		<content:encoded><![CDATA[<p>>> If you have a Mac or Unix machine</p>
<p>Modern macs are unix (for small values of unix)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Weiss</title>
		<link>http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/comment-page-1/#comment-155901</link>
		<dc:creator>John Weiss</dc:creator>
		<pubDate>Fri, 13 Feb 2009 23:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.discovermagazine.com/badastronomy/2009/02/13/epoch-win/#comment-155901</guid>
		<description>Er, and to be clear: that post wasn&#039;t mean to be snarky.  Re-reading it, I worry that it might sound that way.  Frankly, I&#039;m not really concerned about this issue.  I&#039;m just a Stickler for Accuracy.  (Also, I sit on the Axiom Appeals Board.)</description>
		<content:encoded><![CDATA[<p>Er, and to be clear: that post wasn&#8217;t mean to be snarky.  Re-reading it, I worry that it might sound that way.  Frankly, I&#8217;m not really concerned about this issue.  I&#8217;m just a Stickler for Accuracy.  (Also, I sit on the Axiom Appeals Board.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk

Served from: blogs.discovermagazine.com @ 2012-02-14 08:24:22 -->
