<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
>

<channel>
	<title>TechNest Report &#124; TNR &#187; Hardware</title>
	<atom:link href="http://technestreport.com/blog/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://technestreport.com/blog</link>
	<description>We cover, review and analyze the tech industry from head to toe</description>
	<lastBuildDate>Wed, 10 Feb 2010 20:32:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
<!-- podcast_generator="Blubrry PowerPress/1.0.12" mode="advanced" entry="normal" -->
	<itunes:summary>TechNest Report Podcast covers the tech industry from &quot;head to toe!&quot;  The show comes in two flavors: the TNR Daily Bit (airs on M-F) and the TNR Weekly Recap (airs on Saturday).  This is a feed for both shows, which are also available separately.  Alex Luft, Lizette Gagne, Ben Jarman, and guests discuss, rant, praise, and otherwise chew over the events  of the tech industry.  Content focus is less on trivial and ephemeral (such as breaking news). Instead, TechNest Report tries to take a step back, take a nice, long, deep breath, and consider the big picture.

The shows air LIVE Monday through Saturday at 5:30pm EST.  To find out how to catch the show live, please visit live.technestreport.com</itunes:summary>
	<itunes:author>TechNest Report - Alex Luft</itunes:author>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://technestreport.com/blog/wp-content/uploads/2009/06/tnr_podcast_weekly_recap_plus_daily_bit-big.png" />
	<itunes:owner>
		<itunes:name>TechNest Report - Alex Luft</itunes:name>
		<itunes:email>info@technestreport.com</itunes:email>
	</itunes:owner>
	<managingEditor>info@technestreport.com (TechNest Report - Alex Luft)</managingEditor>
	<copyright>Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported-2008-2009</copyright>
	<itunes:subtitle>We cover, review and analyze the tech industry from head to toe (combined feed)</itunes:subtitle>
	<itunes:keywords>technology, tech, business, marketing, management, smart technology, usage, rant, Alex Luft, TechNest Report, TNR, Apple, Mac, Macintosh, Microsoft, PC, gaming,Google, speculation,Linux</itunes:keywords>
	<image>
		<title>TechNest Report | TNR &#187; Hardware</title>
		<url>http://technestreport.com/blog/wp-content/uploads/2009/06/tnr_podcast_weekly_recap_plus_daily_bit-small.png</url>
		<link>http://technestreport.com/blog/category/hardware/</link>
	</image>
	<itunes:category text="Technology">
		<itunes:category text="Tech News" />
	</itunes:category>
	<itunes:category text="Business">
		<itunes:category text="Management &amp; Marketing" />
	</itunes:category>
	<itunes:category text="Technology">
		<itunes:category text="Gadgets" />
	</itunes:category>
		<item>
		<title>The State of FireWire: not here nor there</title>
		<link>http://technestreport.com/blog/2009/07/02/the-state-of-firewire-is-not-here-nor-there/</link>
		<comments>http://technestreport.com/blog/2009/07/02/the-state-of-firewire-is-not-here-nor-there/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 03:24:51 +0000</pubDate>
		<dc:creator>Alex Luft</dc:creator>
				<category><![CDATA[FireWire]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Input-Output]]></category>

		<guid isPermaLink="false">http://technestreport.com/blog/?p=1493</guid>
		<description><![CDATA[Following up an earlier post about some of the reasons Apple picked FireWire over eSATA in the new MacBook Pro range, let&#8217;s take a look at what&#8217;s in store for the future of FireWire.  On the road map to succeed the current FireWire 400 and 800 standards are the aptly-named IEEE 1600 and 3200 ports. [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Ftechnestreport.com%2Fblog%2F2009%2F07%2F02%2Fthe-state-of-firewire-is-not-here-nor-there%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Ftechnestreport.com%2Fblog%2F2009%2F07%2F02%2Fthe-state-of-firewire-is-not-here-nor-there%2F&amp;source=technestreport&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://technestreport.com/blog/wp-content/uploads/2009/07/The-state-of-FireWire.png"><img class="aligncenter size-full wp-image-1617" title="The-state-of-FireWire" src="http://technestreport.com/blog/wp-content/uploads/2009/07/The-state-of-FireWire.png" alt="The-state-of-FireWire" width="300" height="200" /></a>Following up an earlier <a title="Apple picks FireWire, PC does eSATA, and what I/O we can expect in future MacBooks" href="http://technestreport.com/blog/2009/06/20/apple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks/" target="_blank">post</a> about some of the reasons Apple picked FireWire over eSATA in the new MacBook Pro range, let&#8217;s take a look at what&#8217;s in store for the future of FireWire.  On the road map to succeed the current FireWire 400 and 800 standards are the aptly-named IEEE 1600 and 3200 ports.  They are &#8211; you guessed it &#8211; twice as fast as the current implementations of the current IEEE 1394 interface &#8211; FireWire 400 and 800.<span id="more-1493"></span></p>
<h4>Speed-wise</h4>
<p>FireWire 1600 has the ability to push bits at a rate of 1.6Gbit/s (200MB/s), while FireWire 3200 doubles that number to 3.2Gbit/s (400MB/s).  For comparison&#8217;s sake, FireWire 1600 is just 0.1Gbit/s (12.5MB/s) faster than SATA 1.5 while FireWire 3200 is a full 25MB/s (.2Gbit/s) faster than SATA 3.0.  FireWire 1600 and 3200 use the same 9-circuit <strong>beta</strong> connectors as the existing FireWire 800 standard, as opposed to the FireWire 400 connector &#8211; which is the <strong>alpha</strong> connector.  In most cases, this most likely means that if you have a FireWire 800 port, you&#8217;ll be able to connect a FireWire 1600 or a 3200 device without the need for an adapter, yet be limited to 800Mbit/s (the speed of FireWire 800).  Those with a FireWire 400 port (using the alpha connector) will need an adapter to connect peripherals using the new standard but would not be able to operate them at a rate higher than 400Mbit/s.  <!--more--></p>
<h4>Product-wise</h4>
<p>Expect to see FireWire 1600 and 3200 replace the current FireWire 400 and 800 interfaces in the typical fashion: higher-end systems will get the new ports first, which will later make their way into lower-end systems, until &#8211; eventually &#8211; it is seen on most machines (that is, unless netbooks take over the world).  In essence, FireWire 1600 is analogous to today&#8217;s FireWire 400 (destined for lower-end systems), while FireWire 3200 can be equated to FireWire 800 &#8211; which is seen on higher-end machines.  Given the fact that the IEEE 1394 interface has been <a title="Wikipedia - IEEE 1394 interface" href="http://en.wikipedia.org/wiki/IEEE_1394" target="_blank">adopted</a> as the HANA (High-Definition Audio-Video Network Alliance) standard connection interface for A/V component communication and control, it most likely will be very popular with audio/visual devices (as has been the case with the current FireWire 400 and 800 implementations).</p>
<h4>Time-frame-wise</h4>
<p>In December of 2007, the 1394 Trade Association announced that products based on the new FireWire 1600 and 3200 standards will be available before the end of 2008.  Unfortunately, very <a title="Engadget: Symwave demoes firewire 1600 gear" href="http://www.engadget.com/2008/04/09/symwave-demoes-firewire-1600-gear/" target="_blank">few</a> products based on the new spec have been seen.  This is surprising, due to the fact that the spec was made available to manufacturers in October of 2008.  Given this fact, I&#8217;d say that the state of FireWire is not here nor there: older (400 and 800) FireWire specs are being manufactured into current hardware (machines, motherboards, PCI cards, and external equipment), but the newer and faster specs aren&#8217;t to be seen.  What gives?  Perhaps we will bypass the entire next-gen FireWire spec altogether and make the jump to eSATA?  Look out for a follow-up post on this soon.</p>
<div id="crp_related"><h2>You may also like (automatically generated)</h2><ul><li><a href="http://technestreport.com/blog/2009/06/20/apple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks/" rel="bookmark" class="crp_title">Apple picks FireWire, PC does eSATA, and what I/O we can expect in future MacBooks</a></li><li><a href="http://technestreport.com/blog/2008/02/17/does-apple-have-something-against-expresscard-usb-ports-card-slots/" rel="bookmark" class="crp_title">Does Apple have something against ExpressCard?  USB ports?  Card Slots?</a></li><li><a href="http://technestreport.com/blog/2007/05/21/apple-notebook-wishlist-countdown-part-i/" rel="bookmark" class="crp_title">Updated: Apple notebook wish list countdown, Part I: ExpressCard port</a></li><li><a href="http://technestreport.com/blog/2008/02/10/macbook-air-a-machine-lost-in-jobs-reality-distortion-field/" rel="bookmark" class="crp_title">MacBook Air&#8230; A machine lost in Jobs&#8217; reality-distortion field?</a></li><li><a href="http://technestreport.com/blog/2008/10/14/new-macbooks-the-smart-move/" rel="bookmark" class="crp_title">New MacBooks: the smart move</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://technestreport.com/blog/2009/07/02/the-state-of-firewire-is-not-here-nor-there/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Google trike is here! System requirements: specially-trained super-fit riders</title>
		<link>http://technestreport.com/blog/2009/06/20/google-street-view-trike-privacy-japan-europe/</link>
		<comments>http://technestreport.com/blog/2009/06/20/google-street-view-trike-privacy-japan-europe/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 18:37:42 +0000</pubDate>
		<dc:creator>Alex Luft</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Privacy]]></category>

		<guid isPermaLink="false">http://technestreport.com/blog/?p=1494</guid>
		<description><![CDATA[Earlier this week we reported that Google&#8217;s Street View has come under substantial privacy-related criticism in Japan.  The critics were outraged that Google&#8217;s cameras captured the insides of many Japanese backyards.  In leu of the criticism (which is definitely not a first for the web-based service), Google has decided to throw away all captured footage [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Ftechnestreport.com%2Fblog%2F2009%2F06%2F20%2Fgoogle-street-view-trike-privacy-japan-europe%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Ftechnestreport.com%2Fblog%2F2009%2F06%2F20%2Fgoogle-street-view-trike-privacy-japan-europe%2F&amp;source=technestreport&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="aligncenter size-full wp-image-1495" title="google-street-view-trike" src="http://technestreport.com/blog/wp-content/uploads/2009/06/google-street-view-trike.jpeg" alt="google-street-view-trike" width="472" height="328" />Earlier this week we <a title="TNR: Google Street View – privacy concerns: real or imaginary?" href="http://technestreport.com/blog/2009/06/18/google-street-view-privacy-concerns-real-or-imaginary/" target="_blank">reported</a> that Google&#8217;s Street View has come under substantial privacy-related <a title="Slashdot: Google's Streetview Seen As Culturally Insensitive In Japan " href="http://yro.slashdot.org/article.pl?sid=08/08/10/0020211" target="_blank">criticism</a> in Japan.  The critics were outraged that Google&#8217;s cameras captured the insides of many Japanese backyards.  In leu of the criticism (which is definitely <a title="Wikipedia - Google Street View - criticism" href="http://en.wikipedia.org/wiki/Google_Street_View#Privacy_issues" target="_blank">not a first for the web-based service</a>), Google has decided to throw away all captured footage of the 12 cities it has already captured in Japan, and start over.  The company will reposition its cameras 40 centimeters lower (for a total height of 2.05 meters).  Not satisfied with these minor tune-ups to its fleet of Street View vehicles, Google has taken things one step further by releasing the Google Trike.  <span id="more-1494"></span></p>
<p>The three-wheeled super-sized tricycles carry 250 pounds of ballast in the form of &#8220;a mounted Street View camera and a specially-decorated box containing image-collecting gadgetry,&#8221; says the web giant.  Not only will such a device help in places where a standard Street View van is too tall and invades on people&#8217;s privacy by capturing their laundry (or their backyards) on camera, it will also assist Google in tight and small historic places where a regular vehicle simply can&#8217;t fit, like Genoa, Italy.</p>
<p>In fact, that&#8217;s where the new trikes will first be deployed, followed by the United Kingdom &#8211; where the trikes will capture plenty of famous British landmarks.  If you have one in mind, Google is open to <a title="Street View: Explore the biggest cities in the UK with 360 degree street level imagery  " href="http://maps.google.co.uk/help/maps/streetview/" target="_blank"><span style="color: #000000;"><span style="text-decoration: none;">suggestions</span></span></a> and will be working with VisitBritain to pick out the most desirable locations to shoot.  Since it is a fact of life that people and cars will be in the Street View images along with the famous landmarks, Google promises to &#8220;apply our face-blurring and license plate blurring to all these images.&#8221;</p>
<p>One more thing: since the trike does weigh the hefty 250 pounds that it does, it requires a &#8220;<a title="Wikipedia - Lance Armstrong" href="http://en.wikipedia.org/wiki/Lance_Armstrong" target="_blank"><span style="color: #000000;"><span style="text-decoration: none;">specially trained super fit</span></span></a>&#8221; rider.&#8221;  If you fit the descriptions, it might just be your dream job: get fit while traveling the world on Google&#8217;s expense.  Everyone else need not apply.</p>
<div><span style="font-family: Arial;"><span style="line-height: normal;"><br />
</span></span></div>
<div id="crp_related"><h2>You may also like (automatically generated)</h2><ul><li><a href="http://technestreport.com/blog/2009/06/18/google-street-view-privacy-concerns-real-or-imaginary/" rel="bookmark" class="crp_title">Google Street View &#8211; privacy concerns: real or imaginary?</a></li><li><a href="http://technestreport.com/blog/2007/06/19/database-update/" rel="bookmark" class="crp_title">Database update</a></li><li><a href="http://technestreport.com/blog/2009/11/22/breaking-grand-central-website-to-shut-down-december-31/" rel="bookmark" class="crp_title">Breaking: Grand Central Website To Shut Down December 31</a></li><li><a href="http://technestreport.com/blog/2007/06/19/iphone-no-sdk-adobe-apollo-phone-20/" rel="bookmark" class="crp_title">iPhone + no SDK + Adobe Apollo = Phone 2.0?</a></li><li><a href="http://technestreport.com/blog/2008/06/12/a-few-burning-iphone-3g-questions/" rel="bookmark" class="crp_title">A few burning iPhone 3G questions</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://technestreport.com/blog/2009/06/20/google-street-view-trike-privacy-japan-europe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apple picks FireWire, PC does eSATA, and what I/O we can expect in future MacBooks</title>
		<link>http://technestreport.com/blog/2009/06/20/apple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks/</link>
		<comments>http://technestreport.com/blog/2009/06/20/apple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 17:30:16 +0000</pubDate>
		<dc:creator>Alex Luft</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[FireWire]]></category>
		<category><![CDATA[Input-Output]]></category>
		<category><![CDATA[USB]]></category>

		<guid isPermaLink="false">http://technestreport.com/blog/?p=1478</guid>
		<description><![CDATA[When Apple announced its updated line-up of MacBook Pro notebooks at WWDC, I couldn&#8217;t help but notice a certain pattern in the updates: the inclusion of the FireWire 800 port and the exclusion of a much-faster eSATA port.  Let&#8217;s get the facts over with: FireWire and eSATA are both I/O interfaces that handle data transfer [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Ftechnestreport.com%2Fblog%2F2009%2F06%2F20%2Fapple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Ftechnestreport.com%2Fblog%2F2009%2F06%2F20%2Fapple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks%2F&amp;source=technestreport&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="aligncenter size-full wp-image-1490" title="Battle of the ports" src="http://technestreport.com/blog/wp-content/uploads/2009/06/Battle-of-the-ports.png" alt="Battle of the ports" width="590" height="300" />When Apple announced its updated line-up of <a title="Apple MacBook Pro" href="http://www.apple.com/macbookpro" target="_blank">MacBook Pro</a> notebooks at WWDC, I couldn&#8217;t help but notice a certain pattern in the updates: the inclusion of the FireWire 800 port and the exclusion of a much-faster eSATA port.  Let&#8217;s get the facts over with: FireWire and eSATA are both I/O interfaces that handle data transfer much better than USB.  In fact, they can even be called the &#8220;professional&#8217;s choice&#8221; of I/O interface, with USB being more along the lines of the average consumer/computer user.  FireWire 800 transfers data at a rate of 98.25MB/s while eSATA cranks out 300MB/s.  Compare that with USB 2.0&#8242;s rate of 60MB/s and it&#8217;s easy to see why USB is a consumer-level I/O interface.  But why did Apple pick FireWire over the much faster eSATA and what can we expect to be the de-facto standard for powerful data transfer in future Macs?<span id="more-1478"></span><strong>Pure marketing</strong></p>
<p>It&#8217;s no secret that a sizable portion of MacBook and MacBook Pro users (especially the latter) are creative professionals who make a living making, editing, and distributing audio and video.  This market demands the ability to connect external devices such as sound boards, mixers, and high-end video cameras to their computers.  Therefore, it should come as no surprise that <strong>FireWire</strong>, officially known as the IEEE 1394 interface, has been <a title="hanaalliance.org" href="http://www.hanaalliance.org/docs/whitepaper121405.php" target="_blank">adopted</a> as the High-Definition Audio-Video Network Alliance (HANA) <strong>standard connection interface for A/V (audio/visual) component communication and control</strong>.  This is the single most important reason that influenced Apple to include FireWire 800, and not eSATA, across the entire MacBook Pro range.  Also, the fact that FireWire 6 and 8 pin connectors provide power + data transfer in a single cable is just icing on the cake.</p>
<h4>How &#8217;bout me? eSATA&#8230;</h4>
<p>eSATA is <strong>faster</strong> than FireWire 800.  More than 3.05 times faster, to be exact.  Yet the problem with eSATA is that it doesn&#8217;t supply power through the port, meaning that external power must be provided to drive the eSATA device in question.  This power can either come from the wall or from a USB port.  The long and short of it is that eSATA &#8211; as a standard &#8211; requires more than one cable to be fully functional (the eSATA cable plus a power cable).  And this is where the <a title="eSATA/USB combo port" href="http://i275.photobucket.com/albums/jj284/davidli919/DSC00353.jpg" target="_blank">eSATA/USB combo port</a> comes into play.  Standard on many Windows-based notebooks, the eSATA/USB combo port does exactly what it&#8217;s supposed to: eSATA speed coupled with USB power, all in one port, using one wire.  On top of that, the eSATA/USB combo port can be used as a standalone eSATA or USB port, which speaks to the amazing flexibility of the port.  Obviously, eSATA &#8211; in combo form or not &#8211; is absent on the MacBook line in general.  But looking in my crystal ball, I would say it&#8217;s very much possible that future updates to Apple&#8217;s Pro range of notebooks will include the eSATA/USB combo port: it takes up no more port real estate than a USB port, yet provides twice as much functionality.</p>
<h4>Don&#8217;t give up on USB just yet: USB 3.0</h4>
<p>USB 3.0 is the next version of the ever-so-popular connectivity standard.  The main selling point of 3.0 is that it&#8217;s faster than 2.0.  It&#8217;s much faster, with a transfer speed of 625MB/s &#8211; over ten times the rate of USB 2.0 (60MB/s).  But as is the common gripe of pros using USB for large file transfers, these speeds are not sustainable: USB relies on the processor (host) to do all of the work managing the transfers, and is hampered by this.  Using USB, the host can&#8217;t keep a constant transfer rate.  This is not the case with FireWire: instead of relying on the host machine to do all the heavy-lifting, FireWire devices communicate directly, doing all the processing themselves.  The result is a much more steady throughput that is sustainable over large file transfers, while the USB standard is usually good for small file transfers (burst).</p>
<p>All in all, I see the reason why Apple chose FireWire in its new MacBook Pro range of notebooks: it&#8217;s fast, it&#8217;s a good standard, and it works with the audio/video devices that MacBook Pro users demand.  In the future, however, I expect to see a eSATA/USB combo port, along with USB 3.0 ports.  I like to think that these ports complement, rather than compete with one another &#8211; but this might not be the case for Apple: during the introduction of the 13&#8243; MacBook Pro, Apple&#8217;s Phil Schiller hinted that it was a challenge for Apple&#8217;s engineering team to include an SD card slot <strong>along with</strong> a FireWire port.  If this is in fact the case, the eSATA/USB combo port would make the most sense: it doesn&#8217;t add an additional port to the side of the notebook, but shares an already-existing USB port.  Having all three ports would give the pro user the ultimate coonectivity nirvana: USB for convenience, eSATA for speed an external storage, FireWire for compatibility with audio and video devices.  Moreover, including an eSATA/USB combo port would quell the uproar over the removal of the ExpressCard slot in the MacBook Pro range, since that was one of the most popular uses for the slot.  Until then, let&#8217;s hope Apple is thinking along the same lines!</p>
<p>To see how an eSATA/USB combo port would work with an external drive, take a look at <a title="newmodeus: eSATA-USB combo port cable kit (add external hard drive or SSD)" href="http://newmodeus.com/shop/index.php?main_page=product_info&amp;cPath=17&amp;products_id=235" target="_blank">this</a> product.</p>
<p>Thank you for reading.  Please share your opinion with me in the comments &#8211; I want to know what you think!<br />
PS: we also do a podcast!  Just click on the <a title="TNR Podcasts" href="http://podcast.technestreport.com" target="_blank">Podcasts</a> link at the top of the page to listen!</p>
<div id="crp_related"><h2>You may also like (automatically generated)</h2><ul><li><a href="http://technestreport.com/blog/2009/07/02/the-state-of-firewire-is-not-here-nor-there/" rel="bookmark" class="crp_title">The State of FireWire: not here nor there</a></li><li><a href="http://technestreport.com/blog/2008/02/17/does-apple-have-something-against-expresscard-usb-ports-card-slots/" rel="bookmark" class="crp_title">Does Apple have something against ExpressCard?  USB ports?  Card Slots?</a></li><li><a href="http://technestreport.com/blog/2007/05/21/apple-notebook-wishlist-countdown-part-i/" rel="bookmark" class="crp_title">Updated: Apple notebook wish list countdown, Part I: ExpressCard port</a></li><li><a href="http://technestreport.com/blog/2008/02/10/macbook-air-a-machine-lost-in-jobs-reality-distortion-field/" rel="bookmark" class="crp_title">MacBook Air&#8230; A machine lost in Jobs&#8217; reality-distortion field?</a></li><li><a href="http://technestreport.com/blog/2008/10/14/new-macbooks-the-smart-move/" rel="bookmark" class="crp_title">New MacBooks: the smart move</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://technestreport.com/blog/2009/06/20/apple-picks-firewire-pc-does-esata-and-what-io-we-can-expect-in-future-macbooks/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

