<?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"
	>
<channel>
	<title>Comments on: The Next MacBook</title>
	<atom:link href="http://cafe.elharo.com/mac/the-next-macbook/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/mac/the-next-macbook/</link>
	<description>Longer than a blog; shorter than a book</description>
	<pubDate>Tue, 06 Jan 2009 12:16:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: vitachoconutriment</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-176929</link>
		<dc:creator>vitachoconutriment</dc:creator>
		<pubDate>Sun, 06 Jan 2008 17:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-176929</guid>
		<description>I guess sony is trying to make up for the crap it caused in its gaming department lol :-:

~King Reekun</description>
		<content:encoded><![CDATA[<p>I guess sony is trying to make up for the crap it caused in its gaming department lol :-:</p>
<p>~King Reekun</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mokka mit Schlag &#187; My Next Mac</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-150767</link>
		<dc:creator>Mokka mit Schlag &#187; My Next Mac</dc:creator>
		<pubDate>Mon, 05 Nov 2007 12:47:12 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-150767</guid>
		<description>[...] was tempted to wait for the hypothetical, solid state, ultraportable MacBook, but I don&#8217;t really know if any such project exists, or when it will come out if it [...]</description>
		<content:encoded><![CDATA[<p>[...] was tempted to wait for the hypothetical, solid state, ultraportable MacBook, but I don&#8217;t really know if any such project exists, or when it will come out if it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-146424</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Fri, 26 Oct 2007 14:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-146424</guid>
		<description>Apple will make the hardware 10 times better and 10 times fancier looking ;)

Just give them some time to work their miracle. It *will* happen. Solid state disk, 802.11n and firewire 800 to boot.

Now if only the display card won't set on fire during the economical lifespan of my macbook pro, life would be truely enlightning :)</description>
		<content:encoded><![CDATA[<p>Apple will make the hardware 10 times better and 10 times fancier looking <img src='http://cafe.elharo.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Just give them some time to work their miracle. It *will* happen. Solid state disk, 802.11n and firewire 800 to boot.</p>
<p>Now if only the display card won&#8217;t set on fire during the economical lifespan of my macbook pro, life would be truely enlightning <img src='http://cafe.elharo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-134626</link>
		<dc:creator>Pierre</dc:creator>
		<pubDate>Sat, 29 Sep 2007 01:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-134626</guid>
		<description>Ideal MacBook? You meant 802.11n I guess? And Firewire 800.
Steve, please, have a look at this blog! If Sony can make the hardware, can't you just compile Leopard on it and adjust a few drivers?</description>
		<content:encoded><![CDATA[<p>Ideal MacBook? You meant 802.11n I guess? And Firewire 800.<br />
Steve, please, have a look at this blog! If Sony can make the hardware, can&#8217;t you just compile Leopard on it and adjust a few drivers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-117443</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 08 Aug 2007 14:23:09 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-117443</guid>
		<description>I heartily recommend ChronoSync:
http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.htm</description>
		<content:encoded><![CDATA[<p>I heartily recommend ChronoSync:<br />
<a href="http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.htm" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.econtechnologies.com');" rel="nofollow">http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Shaum</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-113869</link>
		<dc:creator>Kevin Shaum</dc:creator>
		<pubDate>Fri, 27 Jul 2007 15:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-113869</guid>
		<description>What about a version control system? A few months ago I put all my docs under Subversion, and it's made it a *lot* easier to keep my various machines in sync. I'm planning on going back soon and partitioning my docs into 'projects', for heavily-used material and archival material (which should also speed up syncing). I'm also considering switching to Mercurial or Bazaar, so I can eliminate the server as a single point of failure.</description>
		<content:encoded><![CDATA[<p>What about a version control system? A few months ago I put all my docs under Subversion, and it&#8217;s made it a *lot* easier to keep my various machines in sync. I&#8217;m planning on going back soon and partitioning my docs into &#8216;projects&#8217;, for heavily-used material and archival material (which should also speed up syncing). I&#8217;m also considering switching to Mercurial or Bazaar, so I can eliminate the server as a single point of failure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliotte Rusty Harold</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-112769</link>
		<dc:creator>Elliotte Rusty Harold</dc:creator>
		<pubDate>Tue, 24 Jul 2007 02:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-112769</guid>
		<description>I tested and ruled out Unison a &lt;a href="http://www.elharo.com/blog/mac/2006/09/07/unison-final-answer/" rel="nofollow"&gt;year ago&lt;/a&gt;. 

Synchronization software is like backup software: it has to be bulletproof to be useful. Misbehaving sync/backup software can do way too much damage through sins of both omission and commission. 

That means it has to be bug free and have a totally obvious interface with no room for confusion. I need to know what I'm syncing and what I'm not. 

To date, most of the third party products fail the user interface test. The notable exception  was Decimus Sync. That was the product with a few crippling bugs on large files they haven't yet fixed. (I should probably check that again. Seems they just released version 6.1, though they haven't updated their web site. However, there are a lot of problem reports for this version in the forum that make me nervous.) Then there are all the iSync based products, which sync only some files but not others. 

I suspect a professional mac sys-admin could eventually make something like Unison or rsync work, but I don't have time for that. I need something that just works.</description>
		<content:encoded><![CDATA[<p>I tested and ruled out Unison a <a href="http://www.elharo.com/blog/mac/2006/09/07/unison-final-answer/"  rel="nofollow">year ago</a>. </p>
<p>Synchronization software is like backup software: it has to be bulletproof to be useful. Misbehaving sync/backup software can do way too much damage through sins of both omission and commission. </p>
<p>That means it has to be bug free and have a totally obvious interface with no room for confusion. I need to know what I&#8217;m syncing and what I&#8217;m not. </p>
<p>To date, most of the third party products fail the user interface test. The notable exception  was Decimus Sync. That was the product with a few crippling bugs on large files they haven&#8217;t yet fixed. (I should probably check that again. Seems they just released version 6.1, though they haven&#8217;t updated their web site. However, there are a lot of problem reports for this version in the forum that make me nervous.) Then there are all the iSync based products, which sync only some files but not others. </p>
<p>I suspect a professional mac sys-admin could eventually make something like Unison or rsync work, but I don&#8217;t have time for that. I need something that just works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bob</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-112765</link>
		<dc:creator>bob</dc:creator>
		<pubDate>Tue, 24 Jul 2007 02:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-112765</guid>
		<description>A 32 GB flash drive won't cut it.  Any Intel-based version of Mac OS X has to include all the PPC versions of all the libraries, because it has to run Rosetta, the PPC emulator.  That requirement almost doubles the size of an x86 OS install.

I'm not saying that 32 GB is unusable: it's quite usable.  I have multiple partitions on my rotating HD, and the OS + Developer tools easily fits on a 25 GB partition.  But I also have all my work files on *another* partition, and the OS one is filled to ~12 GB.  Not so good.  Not really.

If I had to carry my music collection and lots of other infrequently used files, I'd probably just use an iPod as a combination music and mass-storage device.  This would work better with the way I play music anyway.  I don't want to cart my laptop around just to hear tunes.

And I'll go out on a limb and say "multi-touch trackpad", but it'll only work with some applications, or maybe only to zoom the whole scalable GUI of Leopard.

And a pony.  A shiny palomino pony.</description>
		<content:encoded><![CDATA[<p>A 32 GB flash drive won&#8217;t cut it.  Any Intel-based version of Mac OS X has to include all the PPC versions of all the libraries, because it has to run Rosetta, the PPC emulator.  That requirement almost doubles the size of an x86 OS install.</p>
<p>I&#8217;m not saying that 32 GB is unusable: it&#8217;s quite usable.  I have multiple partitions on my rotating HD, and the OS + Developer tools easily fits on a 25 GB partition.  But I also have all my work files on *another* partition, and the OS one is filled to ~12 GB.  Not so good.  Not really.</p>
<p>If I had to carry my music collection and lots of other infrequently used files, I&#8217;d probably just use an iPod as a combination music and mass-storage device.  This would work better with the way I play music anyway.  I don&#8217;t want to cart my laptop around just to hear tunes.</p>
<p>And I&#8217;ll go out on a limb and say &#8220;multi-touch trackpad&#8221;, but it&#8217;ll only work with some applications, or maybe only to zoom the whole scalable GUI of Leopard.</p>
<p>And a pony.  A shiny palomino pony.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://cafe.elharo.com/mac/the-next-macbook/#comment-112752</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Tue, 24 Jul 2007 01:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/mac/the-next-macbook/#comment-112752</guid>
		<description>What's the matter with Unison?  Install it from Fink Commander.  Not a "Mac app', but it does the job in a very cross-platform way, is bidirectional, and is smart about copying only the changes to large files rather than the whole files.</description>
		<content:encoded><![CDATA[<p>What&#8217;s the matter with Unison?  Install it from Fink Commander.  Not a &#8220;Mac app&#8217;, but it does the job in a very cross-platform way, is bidirectional, and is smart about copying only the changes to large files rather than the whole files.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
