<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Abolish Time Zones</title>
	<atom:link href="http://smidg.in/2010/01/17/abolish-time-zones/feed/" rel="self" type="application/rss+xml" />
	<link>http://smidg.in/2010/01/17/abolish-time-zones/</link>
	<description>The Smidgin: A Sporadic Blogger</description>
	<lastBuildDate>Sun, 05 Feb 2012 06:39:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: some1</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4216</link>
		<dc:creator><![CDATA[some1]]></dc:creator>
		<pubDate>Fri, 30 Dec 2011 00:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4216</guid>
		<description><![CDATA[I agree!]]></description>
		<content:encoded><![CDATA[<p>I agree!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noddy</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4187</link>
		<dc:creator><![CDATA[noddy]]></dc:creator>
		<pubDate>Fri, 08 Jul 2011 17:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4187</guid>
		<description><![CDATA[yeah right, and while your at it  why not shorten a second  to ~0.864 of its current length and  make a minute 100 seconds, an hour 100 minutes,  and just have 10 hours in a day.

I dont know what you&#039;d do about the watershed though...]]></description>
		<content:encoded><![CDATA[<p>yeah right, and while your at it  why not shorten a second  to ~0.864 of its current length and  make a minute 100 seconds, an hour 100 minutes,  and just have 10 hours in a day.</p>
<p>I dont know what you&#8217;d do about the watershed though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lenoxus</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4130</link>
		<dc:creator><![CDATA[lenoxus]]></dc:creator>
		<pubDate>Mon, 08 Nov 2010 17:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4130</guid>
		<description><![CDATA[Regarding GlobalMetricTime: The &lt;i&gt;only&lt;/i&gt; problem with that is that ten isn&#039;t such a hot base, and ultimately ought to be discarded altogether. Twelve is where it&#039;s at!

&quot;New&quot; seconds would be either roughly four old ones, or roughly one third of an old one (dpending on how many division you want to make), so it doesn&#039;t jive as well compared to the decimal concept. But, people are used to base-twelve thinking when it comes to hours. Hmm, tough stuff.]]></description>
		<content:encoded><![CDATA[<p>Regarding GlobalMetricTime: The <i>only</i> problem with that is that ten isn&#8217;t such a hot base, and ultimately ought to be discarded altogether. Twelve is where it&#8217;s at!</p>
<p>&#8220;New&#8221; seconds would be either roughly four old ones, or roughly one third of an old one (dpending on how many division you want to make), so it doesn&#8217;t jive as well compared to the decimal concept. But, people are used to base-twelve thinking when it comes to hours. Hmm, tough stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lenoxus</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4129</link>
		<dc:creator><![CDATA[lenoxus]]></dc:creator>
		<pubDate>Mon, 08 Nov 2010 17:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4129</guid>
		<description><![CDATA[One thing I like about this concept is how precisely one could sync events with local daylight. With time zones, you have time &quot;jumping&quot; by margins of an hour (or sometimes half-hour) as you travel. But under this system, you could fine-tune things to match both the actual sunrise/sunset and our circadian rhythms. (It would come to be seen as reasonable for one office to open at 8:23, and another, some miles away, at 8:37.)

The biggest problem would indeed be the lack of cross-cultural understanding about what a given time &quot;means&quot;. So perhaps for every region that was once a zone, governments would establish &quot;official morning time&quot;, corresponding to what was once 7AM (or whatever).

Meanwhile, the whole calendar could use some fixing too…

Months ought to be renamed to each start with a unique letter (in the current system, it takes &lt;i&gt;three letters&lt;/i&gt; to &quot;abbreviate&quot; them! — or two digits, still wasteful). They should &lt;a href=&quot;http://www.halfbakery.com/idea/Rename_20months_20alphabetically&quot; rel=&quot;nofollow&quot;&gt;occur in alphabetical order&lt;/a&gt; (for easy sorting and memorization). Perhaps the same with weekdays, (although there would be some debate over what should be considered the &quot;first&quot; day of the week).

The number of days in each month should follow a consistent pattern — either all of them containing the same number of days (28, 29, 30) with one &quot;small month&quot; at the end of the year, or an &lt;a href=&quot;http://earthcalendar.info/&quot; rel=&quot;nofollow&quot;&gt;alternating pattern of 30 and 31 days&lt;/a&gt;. &quot;&lt;i&gt;Thirty days hath September&lt;/i&gt;…&quot;? Humans shouldn&#039;t need mnemonics for things we made up in the first place!

Most important and sanest of all: years should always start with the same weekday, and the leap day should happen at the end of the year. That way, scheduling holidays for a given institution is way, way easier — you don&#039;t have to worry about whether Fun Day falls on a Wednesday or a Saturday this year (I speak as someone who works for a school). And you would reduce those confusions that arise when someone says &quot;Meet me on Wednesday the 16th&quot; and the 16th isn&#039;t a Wednesday (which one takes priority?). If &lt;i&gt;every&lt;/i&gt; Gemini 16th is a Thursday, you&#039;ll be more likely to ask for clarification. Heck, perhaps dates should come in base 7 instead of 10 (it would still take only two digits to describe the month). That way, knowing the date will mean that you know the day!

Ah, the things that will never happen (at least not until Octember of the year 21-J).]]></description>
		<content:encoded><![CDATA[<p>One thing I like about this concept is how precisely one could sync events with local daylight. With time zones, you have time &#8220;jumping&#8221; by margins of an hour (or sometimes half-hour) as you travel. But under this system, you could fine-tune things to match both the actual sunrise/sunset and our circadian rhythms. (It would come to be seen as reasonable for one office to open at 8:23, and another, some miles away, at 8:37.)</p>
<p>The biggest problem would indeed be the lack of cross-cultural understanding about what a given time &#8220;means&#8221;. So perhaps for every region that was once a zone, governments would establish &#8220;official morning time&#8221;, corresponding to what was once 7AM (or whatever).</p>
<p>Meanwhile, the whole calendar could use some fixing too…</p>
<p>Months ought to be renamed to each start with a unique letter (in the current system, it takes <i>three letters</i> to &#8220;abbreviate&#8221; them! — or two digits, still wasteful). They should <a href="http://www.halfbakery.com/idea/Rename_20months_20alphabetically" rel="nofollow">occur in alphabetical order</a> (for easy sorting and memorization). Perhaps the same with weekdays, (although there would be some debate over what should be considered the &#8220;first&#8221; day of the week).</p>
<p>The number of days in each month should follow a consistent pattern — either all of them containing the same number of days (28, 29, 30) with one &#8220;small month&#8221; at the end of the year, or an <a href="http://earthcalendar.info/" rel="nofollow">alternating pattern of 30 and 31 days</a>. &#8220;<i>Thirty days hath September</i>…&#8221;? Humans shouldn&#8217;t need mnemonics for things we made up in the first place!</p>
<p>Most important and sanest of all: years should always start with the same weekday, and the leap day should happen at the end of the year. That way, scheduling holidays for a given institution is way, way easier — you don&#8217;t have to worry about whether Fun Day falls on a Wednesday or a Saturday this year (I speak as someone who works for a school). And you would reduce those confusions that arise when someone says &#8220;Meet me on Wednesday the 16th&#8221; and the 16th isn&#8217;t a Wednesday (which one takes priority?). If <i>every</i> Gemini 16th is a Thursday, you&#8217;ll be more likely to ask for clarification. Heck, perhaps dates should come in base 7 instead of 10 (it would still take only two digits to describe the month). That way, knowing the date will mean that you know the day!</p>
<p>Ah, the things that will never happen (at least not until Octember of the year 21-J).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GlobalMetricTime</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4128</link>
		<dc:creator><![CDATA[GlobalMetricTime]]></dc:creator>
		<pubDate>Wed, 06 Oct 2010 02:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4128</guid>
		<description><![CDATA[I like getting rid of timezones.  I like getting rid of AM/PM.  I even like redefining what an hour means: how about metric time where 1 day has 10 &quot;hours&quot; and an &quot;hour&quot; has 100 &quot;minutes&quot; and a &quot;minute&quot; has 100 &quot;seconds&quot; then redefine what a &quot;second&quot; is to make all that fit back into into one diurnal day (the average annual time it takes for the sun to hit [0.0 LAT, 0.0 LON] in one rotation).  The new &quot;second&quot; will be 0.864 * the time of a current second - very close.  Total metric time over the entire planet.  It&#039;ll have to happen before an alien civilization visits us anyway.  Why not NOW?]]></description>
		<content:encoded><![CDATA[<p>I like getting rid of timezones.  I like getting rid of AM/PM.  I even like redefining what an hour means: how about metric time where 1 day has 10 &#8220;hours&#8221; and an &#8220;hour&#8221; has 100 &#8220;minutes&#8221; and a &#8220;minute&#8221; has 100 &#8220;seconds&#8221; then redefine what a &#8220;second&#8221; is to make all that fit back into into one diurnal day (the average annual time it takes for the sun to hit [0.0 LAT, 0.0 LON] in one rotation).  The new &#8220;second&#8221; will be 0.864 * the time of a current second &#8211; very close.  Total metric time over the entire planet.  It&#8217;ll have to happen before an alien civilization visits us anyway.  Why not NOW?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4085</link>
		<dc:creator><![CDATA[Jim]]></dc:creator>
		<pubDate>Tue, 19 Jan 2010 13:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4085</guid>
		<description><![CDATA[Very good points. (Krista, see the footnote.) Perhaps what would be required is a sort of  hybrid system. The actual o&#039;clock hours would be standard, but you would have a way of saying &quot;three hours after noon.&quot; Not as easy as 3 p.m., but it would solve the problem.

Steve, I would disagree with your last bit. We&#039;ll eat at 11:30 would make perfect sense in any given place, because people would know that 11:30 is around the time for breakfast, for instance. Just like we now know that 11:30 is around the time for lunch. It&#039;s hard to think about it that way now, but I think the context of the hours would shift. You would only have a problem when out of the given context (like your news example.)]]></description>
		<content:encoded><![CDATA[<p>Very good points. (Krista, see the footnote.) Perhaps what would be required is a sort of  hybrid system. The actual o&#8217;clock hours would be standard, but you would have a way of saying &#8220;three hours after noon.&#8221; Not as easy as 3 p.m., but it would solve the problem.</p>
<p>Steve, I would disagree with your last bit. We&#8217;ll eat at 11:30 would make perfect sense in any given place, because people would know that 11:30 is around the time for breakfast, for instance. Just like we now know that 11:30 is around the time for lunch. It&#8217;s hard to think about it that way now, but I think the context of the hours would shift. You would only have a problem when out of the given context (like your news example.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4084</link>
		<dc:creator><![CDATA[Steve]]></dc:creator>
		<pubDate>Tue, 19 Jan 2010 06:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4084</guid>
		<description><![CDATA[To elaborate on your &quot;what would we lose&quot;, using universal UTC would have the side effect of removing all context-sensitive information from times. This could be very unhelpful in the context of, say, journalism or literature (especially past literature) -- anything read across time zones. For instance, a book that mentions that the protagonist &quot;got up at 5 AM every day and was in bed by 9 each night&quot; has a connotation of self-discipline now which would be completely lost. Compare, for example, &quot;got up at 11 AM every day and went to bed at 3 AM&quot;. Nearly the same phrasing; totally different connotation due to the time shift. Or a news article that mentions that a fire broke out at 2 PM would instead have to specify the time and a context (eg. &quot;2 PM, that is early afternoon here in ____&quot;), since there wouldn&#039;t be any inherent local context for the time. (You could say the news could just say &quot;early afternoon&quot;, but in the interest of specificity that wouldn&#039;t be ideal.) This could even impact business communication, as you would have to specify which shift (evening, morning, etc) when giving hours/meal times/etc if the time was important for giving context. (EG, &quot;we&#039;ll eat at 11:30&quot; would have to be &quot;we&#039;ll eat lunch at 11:30&quot; since 11:30 is arbitrary.) Etc.]]></description>
		<content:encoded><![CDATA[<p>To elaborate on your &#8220;what would we lose&#8221;, using universal UTC would have the side effect of removing all context-sensitive information from times. This could be very unhelpful in the context of, say, journalism or literature (especially past literature) &#8212; anything read across time zones. For instance, a book that mentions that the protagonist &#8220;got up at 5 AM every day and was in bed by 9 each night&#8221; has a connotation of self-discipline now which would be completely lost. Compare, for example, &#8220;got up at 11 AM every day and went to bed at 3 AM&#8221;. Nearly the same phrasing; totally different connotation due to the time shift. Or a news article that mentions that a fire broke out at 2 PM would instead have to specify the time and a context (eg. &#8220;2 PM, that is early afternoon here in ____&#8221;), since there wouldn&#8217;t be any inherent local context for the time. (You could say the news could just say &#8220;early afternoon&#8221;, but in the interest of specificity that wouldn&#8217;t be ideal.) This could even impact business communication, as you would have to specify which shift (evening, morning, etc) when giving hours/meal times/etc if the time was important for giving context. (EG, &#8220;we&#8217;ll eat at 11:30&#8243; would have to be &#8220;we&#8217;ll eat lunch at 11:30&#8243; since 11:30 is arbitrary.) Etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krista</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4083</link>
		<dc:creator><![CDATA[Krista]]></dc:creator>
		<pubDate>Mon, 18 Jan 2010 23:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4083</guid>
		<description><![CDATA[&quot;if, for example, the sun was always directly overhead at five o’clock p.m ...&quot; 

If we&#039;re going to ditch time zones, than for goodness&#039; sake, let&#039;s get rid of the 12 hour clock while we&#039;re at it! 17 hours, no 5 pm :)]]></description>
		<content:encoded><![CDATA[<p>&#8220;if, for example, the sun was always directly overhead at five o’clock p.m &#8230;&#8221; </p>
<p>If we&#8217;re going to ditch time zones, than for goodness&#8217; sake, let&#8217;s get rid of the 12 hour clock while we&#8217;re at it! 17 hours, no 5 pm :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

