<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Noel Schutt &#187; Technology</title>
	<atom:link href="http://schutt.org/blog/category/technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://schutt.org/blog</link>
	<description></description>
	<lastBuildDate>Wed, 21 Jul 2010 16:15:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Customizing Mac OS X PDF Services</title>
		<link>http://schutt.org/blog/2009/08/osx-pdf-services/</link>
		<comments>http://schutt.org/blog/2009/08/osx-pdf-services/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 22:46:06 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[OS X]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=360</guid>
		<description><![CDATA[One useful feature of OS X is the built in PDF handling. It is always easy to export a file as a PDF, and to do some basic editing of PDF files. A post on Mac OS X Hints today got me looking at some customizations. The hint is that creating an alias in the [...]]]></description>
			<content:encoded><![CDATA[<p>One useful feature of OS X is the built in PDF handling. It is always easy to export a file as a PDF, and to do some basic editing of PDF files. A <a href="http://www.macosxhints.com/article.php?story=20090817002247614" title="Add a Save to PDF directory to your Print options">post</a> on Mac OS X Hints today got me looking at some customizations. The hint is that creating an alias in the proper directory adds an item to the PDF menu. This can be done through Finder, or through the command line:</p>
<p><code>cd ~/Libary/PDF\ Services<br />
ln -s ~/path/ "descriptive_alias"</code></p>
<p>You may have to create the directory <code>~/Libary/PDF Services</code>. Some people recommend using the directory <code>/Libary/PDF Services</code>, but this is bad style unless you <em>really</em> want the change to be universal. Even if you are the only user on the computer, it is safer to use the <code>Library</code> folder under your user account.</p>
<p>When looking in the <code>/Libary/PDF Services</code> directory, I noticed that the contents are just Automator workflows. This means it is easy for non-programmers to customize the behavior. One option that I somehow hadn&#8217;t noticed before today is <code>Save PDF to Web Receipts Folder.pdfworkflow</code>. With online billing this is incredibly useful. I typically use the &#8220;Save PDF as&#8221; option, saving the PDF in this year&#8217;s receipts directory, with the date as a prefix. This makes receipts for monthly bills easy to find. I looked at &#8220;Save PDF to Web Receipts Folder&#8221; to see how easy it would be to alter to my preferred style. Instead of being an Automator workflow, this is actually a Python script and a few property lists. Great! Python is my favorite language. I copied the files to <code>~/Libary/PDF Services</code> and edited them. The Python script is in a file named <code>tool</code>. This script is well written, making it easy to modify. Here are the basic changes:</p>
<ul>
<li>Because I want to use timestamps, I added <code>import time</code> after the other import statements.</li>
<li>I changed the <code>destDirectory</code> to my preferred directory. The script already creates the destination directory if it doesn&#8217;t exist, so altering the directory by date is easy, I added <code>destDirectory = os.path.join(destDirectory, time.strftime("%Y"))</code> to automatically append the subdirectory for the year.</li>
<li>The file uses the title of the webpage as the filename. To add the date as a prefix, add the line <code>title = "%s-%s" % (time.strftime( "%Y%m%d"), title)</code> to the build path section. You can easily customize the date format.</li>
<li>I  prefer lowercase filenames, so I added <code>filename = filename.lower()</code> to the <code>safeFilename</code> function.</li>
<li>If a file with this name already exists, the script appends a number to the name. I prefer different character than the default, so I changed it.</li>
</ul>
<p>The final step was to I update the property list files so that the PDF menu shows the name I gave the command, instead of the original name from Apple.</p>
<p>I now have an even quicker way to save my receipts. Because the program is automatically generating the filenames using my preferences, I don&#8217;t have to change the name every time, and can avoid some typos and incorrect dates.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/08/osx-pdf-services/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Voicemail</title>
		<link>http://schutt.org/blog/2009/07/voicemail/</link>
		<comments>http://schutt.org/blog/2009/07/voicemail/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 00:33:56 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[telephone]]></category>
		<category><![CDATA[voicemail]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=287</guid>
		<description><![CDATA[One of the many modern &#8216;conveniences&#8217; that actually take more time than they save is voicemail. Answering machines and voicemail are occasionally useful, but more often than not, someone just leaves a rambling message with details they end up repeating when you call them back. Fortunately, Caller ID has mostly eliminated the need for voicemail: [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://schutt.org/blog/wp-content/uploads/2009/07/20090705-162111-edited-88x150.jpg" alt="Motofone F3" title="Motofone F3" width="88" height="150" class="alignright size-thumbnail wp-image-289" /></p>
<p>One of the many modern &lsquo;conveniences&rsquo; that actually take more time than they save is voicemail. Answering machines and voicemail are occasionally useful, but more often than not, someone just leaves a rambling message with details they end up repeating when you call them back. Fortunately, Caller ID has mostly eliminated the need for voicemail: if you need to leave a message, I probably need to return your call. Since visual voicemail hasn&#8217;t yet been universally adopted&#8212;and some people still leave voicemails&#8212;I sometimes have to check my voicemail account. This has allowed phone companies to waste tons of customer time by forcing us to listen to long instructions describing voicemail. There are no obvious ways to avoid this wasted time. Thanks to <a href="http://pogue.blogs.nytimes.com/2009/07/29/how-to-bypass-stupid-voicemail-instructions/" title="How to Bypass Stupid Voicemail Instructions">David Pogue</a>, I learned the non-obvious way, &ldquo;1 * #&rdquo;. If you are leaving a voice mail, one of those will probably get you out of listening to the pointless 30 second message.</p>
<p>You can look in the voicemail help for your carrier to find the correct code for your own voicemail.</p>
<ul>
<li>T-Mobile: <a href="http://support.t-mobile.com/knowbase/root/public/tm30112.pdf" title="T-Mobile VoiceMail shortucts">VoiceMail Shortcuts</a></li>
<li>Verizon: <a href="http://wirelesssupport.verizon.com/how_to_use/basic_voice_mail.html" title="Verizon voicemail instructions">Voice Mail Instructions</a>; different instructions depending on your region</li>
<li>AT&amp;T: <a href="http://www.wireless.att.com/learn/en_US/pdf/3961_Lucent_VM_QuickGuide.pdf" title="voicemail quickguide">Voicemail Quickguide</a></li>
<li>Sprint: gave up on search; different instructions by phone</li>
</ul>
<p>Source: <a href="http://www.livedigitally.com/2007/03/16/skipping-voicemail-greetings-one-star-pound/" title="LIVEdigitally: skip voicemail greeting">LIVEdigitally</a> through <a href="http://pogue.blogs.nytimes.com/2009/07/29/how-to-bypass-stupid-voicemail-instructions/" title="How to Bypass Stupid Voicemail Instructions">Pogue&#8217;s Posts</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/07/voicemail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MacBook screens</title>
		<link>http://schutt.org/blog/2009/07/macbook-screens/</link>
		<comments>http://schutt.org/blog/2009/07/macbook-screens/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 01:37:09 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[glare]]></category>
		<category><![CDATA[MacBook]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=281</guid>
		<description><![CDATA[There are rumors that Apple may reintroduce matte screens as an option on their notebooks. Apple can&#8217;t return to glare free displays soon enough! I&#8217;m looking forward to buying an aluminum computer once they fix this design flaw. The latest 13 inch MacBook Pro would be almost perfect with an anti-glare screen. [Update 2009-08-11] Anti-glare [...]]]></description>
			<content:encoded><![CDATA[<p>There are <a href="http://arstechnica.com/apple/2009/07/dont-call-it-a-comeback-matte-apple-displays-may-reappear.ars">rumors</a> that Apple may <a href="http://www.appleinsider.com/articles/09/07/15/apple_may_extend_antiglare_display_option_to_more_macs.html"> reintroduce matte screens</a> as an option on their notebooks. Apple can&#8217;t return to glare free displays soon enough! I&#8217;m looking forward to buying an aluminum computer once they fix this design flaw. The latest 13 inch MacBook Pro would be almost perfect with an anti-glare screen.</p>
<p><span class="update">[Update 2009-08-11]</span> Anti-glare is <a href="http://arstechnica.com/apple/news/2009/08/matte-display-option-makes-a-quiet-return-to-15-macbook-pro.ars" title="Ars Technica">back</a> on the 15 inch MacBook Pro! Now for the 13 inch&#8230;</p>
<p><span class="update">[Clarification 2009-08-24]</span> By anti-glare, I don&#8217;t mean a matte display. Keep the glass covering, but use anti-reflection coating. The glass is nice, but reflections make the displays unusable.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/07/macbook-screens/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>University server &#8220;hacked&#8221;</title>
		<link>http://schutt.org/blog/2009/05/university-server/</link>
		<comments>http://schutt.org/blog/2009/05/university-server/#comments</comments>
		<pubDate>Tue, 19 May 2009 20:14:56 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[crack]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[IT]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=218</guid>
		<description><![CDATA[I just received an email from the university saying that the server for faculty and student webpages has been compromised. The message goes on to say it was due to a Microsoft bug and that &#8220;pages were defaced, indicating they were hacked.&#8221; This one email shows two serious problems. The first is that University Computing [...]]]></description>
			<content:encoded><![CDATA[<p>I just received an <a href="https://apps.bsu.edu/CommunicationsCenter/Story.aspx?CategoryID=154&#038;MessageGuid=5E72D3EB-1D0B-4F47-996E-0D54B20AE2C2&#038;OptIn=Y" title="announcement">email</a> from the university saying that the server for faculty and student webpages has been compromised. The message goes on to say it was due to a Microsoft bug and that &#8220;pages were defaced, indicating they were hacked.&#8221; This one email shows two serious problems. The first is that University Computing Services doesn&#8217;t even know enough to say the server was &#8220;vandalized by a cracker.&#8221; Instead, they misuse the word hacker. It is one thing when an average person makes this mistake, but it is a sign of incompetence when it comes from an IT department. The second problem is that they are using a <a href="http://www.gamesforwindows.com/en-US/Pages/index.aspx" title="gaming">gaming operating system</a> on a server, instead of a <a href="http://www.freebsd.org/" title="server OS">proper server OS</a>. But hey, what do you expect from a university that wastes money <a href="http://www.blackboard.com/" title="pain and suffering">Blackboard</a> (which makes even MS look good), instead of using one of the many superior open source alternatives. There is good news though. Yesterday I learned that my undergrad university&#8217;s IT department is replacing some of their Windows servers with Unix. (The <a href="http://cse.taylor.edu/" title="TU CSE">CSE department</a> has always had Unix/Linux servers.)</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/05/university-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Movie menus</title>
		<link>http://schutt.org/blog/2009/04/movie-menus/</link>
		<comments>http://schutt.org/blog/2009/04/movie-menus/#comments</comments>
		<pubDate>Sun, 26 Apr 2009 21:41:18 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Television]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[CRAP]]></category>
		<category><![CDATA[DVD]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=196</guid>
		<description><![CDATA[I just watched a couple episodes of Season Three of Rocky and Bullwinkle on DVD. This is a great show, but the DVD collection is an example of something that has been bugging me for years. I&#8217;m sick of the silly animated menus on movies. They were moderately interesting the first four times ten years [...]]]></description>
			<content:encoded><![CDATA[<p>I just watched a couple episodes of Season Three of <a href="http://en.wikipedia.org/wiki/Rocky_and_bullwinkle" title="Rocky and Bullwinkle">Rocky and Bullwinkle</a> on DVD. This is a great show, but the DVD collection is an example of something that has been bugging me for years.</p>
<p>I&#8217;m sick of the silly animated menus on movies. They were moderately interesting the first four times ten years ago. Then they became more and more annoying. I don&#8217;t want to put a DVD in, wait several minutes to get to the main menu, scroll to scene selection, watch an animation, select a scene, then start the movie. I want to put the disc in and have the movie start. If I want the menu, I&#8217;ll hit the menu button. If I want to watch trailers, I&#8217;ll select trailers. Direct access was supposed to be one of the benefits of DVD over tape. But since many DVD players don&#8217;t let you skip all the animations, you may as well be fast forwarding through trailers. Not that I want to go back to tape, but new technology should make life better, not just different.</p>
<p>The second problem is the <a href="http://schutt.org/blog/2008/11/crap/" title="Controlled Reading and Playing">CRAP</a> included on DVD and Blu-ray. It is bad on DVD. The CRAP on Blu-ray it is so bad I refuse to ever buy a Blu-ray disc.</p>
<p>I may as well include a third problem: How do all rental DVDs end up scratched? Are people playing frisbee with them? Using them as coasters? I have never scratched a CD or DVD, yet most rental DVDs are scratched enough to loose whole scenes.</p>
<p>I hope whatever high-definiton format (<a href="http://en.wikipedia.org/wiki/Holographic_Versatile_Disc" title="Holographic Versatile Disc">HVD</a>?) we end up with in a couple years fixes these problems. Maybe we&#8217;ll even get a decent frame rate, 24 or 30 frames per second flickers way too much&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/04/movie-menus/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Crash</title>
		<link>http://schutt.org/blog/2008/12/crash/</link>
		<comments>http://schutt.org/blog/2008/12/crash/#comments</comments>
		<pubDate>Wed, 10 Dec 2008 02:50:01 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[hard drive crash]]></category>
		<category><![CDATA[MacBook]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=93</guid>
		<description><![CDATA[The hard drive on my MacBook crashed. It took two weeks to get it back the way I like it. It took a week to get a new drive and do a temporary restore. I then had to use it as-is for a few days. I then went back and did a fresh install and [...]]]></description>
			<content:encoded><![CDATA[<p>The hard drive on my MacBook crashed. It took two weeks to get it back the way I like it. It took a week to get a new drive and do a temporary restore. I then had to use it as-is for a few days. I then went back and did a fresh install and spent a few days installing programs and making custom settings. It took so long because I forgot a couple of my usual backups. Now I am obsessed with creating an automatic archiving system. I have a good start. I&#8217;ll post details when I know it is bombproof. I need to convince myself to study for another week before finishing my scripts.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/12/crash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Controlled Reading And Playing</title>
		<link>http://schutt.org/blog/2008/11/crap/</link>
		<comments>http://schutt.org/blog/2008/11/crap/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 16:58:54 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[copyright]]></category>
		<category><![CDATA[CRAP]]></category>
		<category><![CDATA[DRM]]></category>
		<category><![CDATA[ethics]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=84</guid>
		<description><![CDATA[After a couple frustrating weeks with computers, we have been talking about copy-protection. With the switch to DTV, Blu-ray, and DisplayPort, it is getting harder to avoid buying copy-controlled products. Avoiding Blu-ray is easy, but avoiding encrypted DisplayPort will be harder. Luke and Adam wanted to use the acronym FARCE, but we couldn&#8217;t settle on [...]]]></description>
			<content:encoded><![CDATA[<p>After a couple frustrating weeks with computers, we have been talking about copy-protection. With the switch to DTV, Blu-ray, and DisplayPort, it is getting harder to avoid buying copy-controlled products. Avoiding Blu-ray is easy, but avoiding encrypted DisplayPort will be harder. <a href="http://legoboy.com/" title="Legoboy">Luke</a> and Adam wanted to use the acronym FARCE, but we couldn&#8217;t settle on a definition. The word &lsquo;crap&rsquo; came to mind. This gave a convenient definition: Controlled Reading and Playing. I thought may have heard this term before. I found a few references to the acronym CRAP for DRM on <a href="http://blogs.zdnet.com/BTL/?p=2416" title="ZDNet">ZDNet</a>, but using a different definition: Content Restriction, Annulment, and Protection. (A good video explanation: <a href="http://news.zdnet.com/2422-13569_22-156220.html" title="A load of CRAP">A load of C.R.A.P.</a> by ZDNet Executive Editor David Berlind.) Richard Stallman saw the article and <a href="http://blogs.zdnet.com/BTL/?p=2582" title="ZDNet">suggested</a> another definition: Cancellation, Restriction and Punishment. All of these definitions work. Please start using the acronym CRAP instead of the euphemism DRM.</p>
<p>P.S. For those less informed on the ethics of technology: DRM is an acronym for Digital Rights Management. It is used as a euphemism for copy-control. Some companies try to control the ethical&#8211;and legal&#8211;fair use of music, video, and text. A common method is encryption designed to only allow files to be accessed on approved devices. Good examples are Blu-ray disks and some PDF files. These encryption systems are superfluous and unethical. This is why the euphemism DRM commonly makes lists of technology terms to avoid: <a href="http://www.gnu.org/philosophy/words-to-avoid.html#DigitalRightsManagement" title="gnu.org: Philosophy">Some Confusing or Loaded Words and Phrases that are Worth Avoiding</a>, and <a href="http://pogue.blogs.nytimes.com/2008/10/16/tech-terms-to-avoid/" title="NY Times: David Pogue:Tech Terms to Avoid">Tech Terms to Avoid</a>. We settled on the term CRAP: Controlled Reading and Playing.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/11/crap/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>&#8220;Drill, Baby, Drill!&#8221;</title>
		<link>http://schutt.org/blog/2008/10/drill-baby-drill/</link>
		<comments>http://schutt.org/blog/2008/10/drill-baby-drill/#comments</comments>
		<pubDate>Thu, 16 Oct 2008 12:00:06 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Cars]]></category>
		<category><![CDATA[Climate]]></category>
		<category><![CDATA[Energy]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[conservation]]></category>
		<category><![CDATA[economics]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=75</guid>
		<description><![CDATA[&#8220;Drill, Baby, Drill!&#8221; We have heard this phrase constantly since the Republican convention. The thought behind this chant is that increased American oil production will lead to lower gas prices. This idea is based on supply and demand. With a constant demand, increasing supply should lower the price of a resource. Drilling in the US [...]]]></description>
			<content:encoded><![CDATA[<p>&ldquo;Drill, Baby, Drill!&rdquo; We have heard this phrase constantly since the Republican convention. The thought behind this chant is that increased American oil production will lead to lower gas prices. This idea is based on supply and demand. With a constant demand, increasing supply should lower the price of a resource. Drilling in the US produces more oil, so prices should go down. This reduces the cost of energy and lessens our dependance on foreign oil from often unfriendly countries.</p>
<p>This is silly.</p>
<p>The idea that increased domestic oil production will lower prices has several flaws. &ldquo;Drill, baby, drill&rdquo; oversimplifies supply and demand. It ignores physics. It assumes that oil companies are altruistic. It forgets that oil is a fungible commodity on a world market.</p>
<p>I&#8217;ll start with physics. Oil is called a fossil fuel for a reason. It was deposited in the past. The supply isn&#8217;t increasing. The law of conservation of mass doesn&#8217;t make a special exception for oil. There is only so much petroleum in the earth. Oil doesn&#8217;t magically reappear some time after a well runs dry. Once we use oil, it is gone.  Oil isn&#8217;t produced, it is tapped from limited reservoirs. Increasing the rate of withdraw doesn&#8217;t increase supply, it decreases the time the fixed supply lasts.</p>
<p>&ldquo;Drill, baby, drill&rdquo; forgets that oil companies are for-profit businesses. It assumes that an increase in their ability to tap oil means they will increase availability, lowering prices. This action wouldn&#8217;t make sense for oil companies.  As dealers of a limited resource, their goal is to make as much money as possible off the resource before it is gone. They need to maximize their lifetime profit per barrel. Increasing the rate of delivery to higher than demand lowers profits. Lowering the rate of delivery leads to higher prices. Using this basic supply and demand idea, it is in the interest of oil companies to decrease the rate of production.</p>
<p>This is also an oversimplification. Increases in oil prices encourages people to look into alternatives. As more people switch to alternatives, the demand for petroleum decreases, leading to lower prices. The profit maximizing strategy for oil companies is to keep delivery as low as possible to maximize the price per barrel, but high enough that demand doesn&#8217;t decrease. This is what they are doing.</p>
<p>To make this strategy more effective, they are also pursuing political and public relations. They admit that we need more than oil, but then claim that alternatives aren&#8217;t ready yet. This helps lower the interest in alternatives, keeping oil demand high. The high price and demand encourage people to thing that increasing availability will lower prices. This lets oil companies claim that they would increase production, but these pesky taxes and environmental regulations are in the way. So the call goes out to practically give them public land and have the public take the responsibility for cleaning up later. Now they are not only maximizing profit and ensuring demand, they are lowering future costs. The calls for drilling now are exactly what the oil companies need to maximize their long term petroleum profits.</p>
<p>The calls for &ldquo;increased domestic production&rdquo; to lower prices also ignore the fact that oil is a fungible commodity. The oil tapped in the US isn&#8217;t reserved strictly for use in the US. Increasing delivery rate in one country increases the rate for the world. Any price change in the US would be the result of a price change on world markets. While the remaining supplies of petroleum in the US sound large compared to American consumption, what matters to price is how they compare to world supplies. While American oil consumption is very high, consumption outside the US is increasing faster. This means that any change in American delivery is becoming less important.</p>
<p>The call for more drilling ignores the fact that it takes time to create the infrastructure to make newly tapped petroleum useful. Most estimates I have seen say that the soonest we would get oil from new American wells would be ten years. Then the oil would be withdrawn over several years. So the best case is we add a little oil to the world market from ten to twenty years from now. There no short term decrease in gas prices. Only a ten year delay. We are then left in the same position as now, but with no reserves.</p>
<p>The solution to the cost of energy in the US isn&#8217;t increased tapping of oil. The lag between drilling and delivery would be better used to increase efficiency, decrease demand, and switch to renewable energy sources.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/10/drill-baby-drill/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who Killed the Electric Car?</title>
		<link>http://schutt.org/blog/2008/06/who-killed-the-electric-car/</link>
		<comments>http://schutt.org/blog/2008/06/who-killed-the-electric-car/#comments</comments>
		<pubDate>Thu, 12 Jun 2008 17:32:22 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Climate]]></category>
		<category><![CDATA[Energy]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[documentary]]></category>
		<category><![CDATA[electric car]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/2008/06/who-killed-the-electric-car/</guid>
		<description><![CDATA[I finally got around to watching Who Killed the Electric Car?. It is a very good documentary. I have been reading about electric vehicles the past few months, and the movie inspired me to start looking again.]]></description>
			<content:encoded><![CDATA[<p>I finally got around to watching <a href="http://www.whokilledtheelectriccar.com/" title="Who Killed the Electric Car? Official Site">Who Killed the Electric Car?</a>. It is a very good documentary. I have been reading about electric vehicles the past few months, and the movie inspired me to start looking again.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/06/who-killed-the-electric-car/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FORTRAN</title>
		<link>http://schutt.org/blog/2008/05/fortran/</link>
		<comments>http://schutt.org/blog/2008/05/fortran/#comments</comments>
		<pubDate>Tue, 13 May 2008 16:38:56 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[FORTRAN]]></category>
		<category><![CDATA[programing]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/2008/05/fortran/</guid>
		<description><![CDATA[In college, before video games, we would amuse ourselves by posing programming exercises. One of the favorites was to write the shortest self-reproducing program. Since this is an exercise divorced from reality, the usual vehicle was FORTRAN. Actually, FORTRAN was the language of choice for the same reason that three-legged races are popular. &#8211;Ken Thompson, [...]]]></description>
			<content:encoded><![CDATA[<blockquote><p>In college, before video games, we would amuse ourselves by posing programming exercises. One of the favorites was to write the shortest self-reproducing program. Since this is an exercise divorced from reality, the usual vehicle was FORTRAN. Actually, FORTRAN was the language of choice for the same reason that three-legged races are popular. &#8211;Ken Thompson, &ldquo;<a href="http://cm.bell-labs.com/who/ken/trust.html" title="Reflections on Trusting Trust">Reflections on Trusting Trust</a>&rdquo; 1984</p></blockquote>
<p>Ah, yes, the joys of FORTRAN.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2008/05/fortran/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
