<?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>Coyote Tracks &#187; books</title>
	<atom:link href="http://kagan.mactane.org/blog/tag/books/feed/" rel="self" type="application/rss+xml" />
	<link>http://kagan.mactane.org/blog</link>
	<description>The prints of an Internet-enabled coyote.</description>
	<lastBuildDate>Tue, 31 Jan 2012 03:26:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>What Are We Giving Up With E-Text?</title>
		<link>http://kagan.mactane.org/blog/2011/09/24/what-are-we-giving-up-with-e-text/</link>
		<comments>http://kagan.mactane.org/blog/2011/09/24/what-are-we-giving-up-with-e-text/#comments</comments>
		<pubDate>Sat, 24 Sep 2011 22:19:30 +0000</pubDate>
		<dc:creator>Kai MacTane</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bad ideas]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[rants]]></category>
		<category><![CDATA[the world-wide conversation]]></category>
		<category><![CDATA[trends]]></category>
		<category><![CDATA[where are we going?]]></category>

		<guid isPermaLink="false">http://kagan.mactane.org/blog/?p=395</guid>
		<description><![CDATA[Engineering is about tradeoffs, and each technology has its advantages and drawbacks. Whenever we leave one technology behind and adopt a new one, we&#8217;re sacrificing something. We may be making a terrific trade, getting a hundred times as much cool stuff as give up&#160;&#8212; but we&#8217;re still giving up something, and we should be aware [...]]]></description>
			<content:encoded><![CDATA[<p>Engineering is about tradeoffs, and each technology has its advantages and drawbacks. Whenever we leave one technology behind and adopt a new one, <strong>we&#8217;re sacrificing something</strong>. We may be making a terrific trade, getting a hundred times as much cool stuff as give up&nbsp;&mdash; but we&#8217;re still giving up <em>something</em>, and we should be aware of what it&nbsp;is.</p>
<p>We&#8217;re currently moving away from paper printing, replacing physical books with e&#x2011;books and text readers. We need to look at what we&#8217;re giving up in the&nbsp;process.</p>
<p>Lev Grossman recently wrote an article for the <cite>New York Times</cite>&#8216;s Sunday Book Review, <a href="http://www.nytimes.com/2011/09/04/books/review/the-mechanic-muse-from-scroll-to-screen.html">&#8220;From Scroll to Screen&#8221;</a>. In it, he points out how our current book format, <em>the <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Codex">codex</a></em> (multiple pages bound in a rectangular shape between two covers) took over from <em>the <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Scroll">scroll</a></em> (a single long sheet of paper wrapped around a rod or roller). He cites <strong>easy random access</strong> as the codex&#8217;s chief benefit, and an absolutely critical&nbsp;one.</p>
<blockquote><p>We usually associate digital technology with nonlinearity, the forking paths that Web surfers beat through the Internet&#8217;s underbrush as they click from link to link. But e&#x2011;books and nonlinearity don&#8217;t turn out to be very compatible. Trying to jump from place to place in a long document like a novel is painfully awkward on an e-reader, like trying to play the piano with numb fingers. You either creep through the book incrementally, page by page, or leap wildly from point to point and search term to search term. It&#8217;s no wonder that the rise of e-reading has revived two words for classical-era reading technologies: scroll and tablet. That&#8217;s the kind of reading you do in an e&#x2011;book. </p></blockquote>
<p>Not to use too much of Grossman&#8217;s text, but another section near the end of his essay points out a critical aspect of the sacrifice we&#8217;re making as we move toward e&#x2011;books:</p>
<blockquote><p>[I]f we stop reading on paper, we should keep in mind what we&#8217;re sacrificing: that nonlinear experience, which is unique to the codex. You don&#8217;t get it from any other medium — not movies, or TV, or music or video games. The codex won out over the scroll because it did what good technologies are supposed to do: It gave readers a power they never had before, power over the flow of their own reading experience.</p></blockquote>
<p>Except that&#8217;s not the only sacrifice involved. That&#8217;s simply the technological, UX sacrifice&nbsp;&mdash; but <em>we&#8217;re also making a societal</em> sacrifice, and it&#8217;s one that may be even worse. <strong>We&#8217;re sacrificing a huge number of readers</strong>, many of whom become writers and boosters of text as a mode of communication.</p>
<p>Recently, Seanan McGuire wrote <a href="http://seanan-mcguire.livejournal.com/390067.html">&#8220;Across the Digital Divide&#8221;</a>, in which she talks about what it&#8217;s like to be poor, and about how the current (official, U.S. government) measures of poverty are based on what was available in 1955. <span id="more-395"></span> Noting that computers and e&#x2011;book readers didn&#8217;t exist then, and so aren&#8217;t even noticed in modern-day poverty measurements, she then unleashes her main&nbsp;point:</p>
<blockquote><p>[E]very time a discussion of ebooks turns, seemingly inevitably, to &#8220;Print is dead, traditional publishing is dead, all smart authors should be bailing to the brave new electronic frontier,&#8221; what I hear, however unintentionally, is &#8220;Poor people don&#8217;t deserve to&nbsp;read.&#8221;</p></blockquote>
<p>She notes that this isn&#8217;t due to malice; it&#8217;s just hard for those of us with lots of money and bandwidth to see across the divide that (at least) 1 in 5 Americans are still on the downside of. But she also points out that seemingly-simple &#8220;remedies&#8221; like a low-cost e-reader program for poor kids, or even giving them away free, will not solve the problem. That doesn&#8217;t address concerns ranging from bandwidth to&nbsp;theft.</p>
<div class="notice">As an aside: The statement &#8220;print is dead&#8221;, in 2011, is as foolishly wrong as &#8220;we have a Moon colony&#8221; would be. We might get a Moon colony some day. And print is certainly going through some decline, but it&#8217;s still too soon to say whether it will ever fade away completely. (We&#8217;re still waiting for the &#8220;<a href="http://en.wikipedia.org/wiki/Network_Computer">Network Computer</a>&#8221; to take over, for Java to render all other programming languages obsolete, and for decent AI,&nbsp;too.)</div>
<p>Even if we assume that print is about to die, that it is inevitable and the most we can do is make our peace with the oncoming new technology, there are still things we can and must do to ensure that it doesn&#8217;t impoverish our society by taking literate expression with it. As McGuire says:</p>
<blockquote><p>We <em>need</em> paper books to endure. Every one of us, if we can log onto this site and look at this entry, is a &#8220;have&#8221; from the perspective of a kid living in an apartment with cockroaches in the walls and junkies in the unit beneath them. A lot of the time, the arguments about the coming ebook revolution forget that the &#8220;have nots&#8221; also exist, and that we need to take care of them. (emphasis in&nbsp;original)</p></blockquote>
<p>Jennifer Brozek&#8217;s &#8220;Poverty and Books&#8221; covers a lot of the same territory, describing how she got her love of reading and words from library books and second- and third-hand books. Note that Ms. Brozek is now an award-winning author and editor, and like Ms. McGuire, is a rising talent in the genre fiction scene. If we ignore their advice, we risk throwing away 20%&nbsp;&mdash; or more&nbsp;&mdash; of the next generation of excellent&nbsp;writers.</p>
<p>That&#8217;s not a price I want to&nbsp;pay.</p>
<p>Finally, Dreamwidth user Elf points out that <strong>the social contract being promoted by e&#x2011;book publishers is essentially and profoundly selfish</strong>. In <a href="http://elf.dreamwidth.org/459611.html">&#8220;The Selfishness of Ebooks&#8221;</a>, she tells a tale that she tags as &#8220;potentially triggery for bibliophiles&#8221;, which turned out to be a good warning in my (bibliophilic) opinion. Her tale involves <span style="cursor: help; border-bottom: 1px dotted;" title="someone reading a book by a campfire, then *tearing out each page as he finished it and burning it in the fire*">something you can mouse over to read, but don&#8217;t say you haven&#8217;t been warned</span> &#8211; stripped of the gruesome details, it involves someone who would habitually destroy books while reading them, obliterating each page as soon as he&#8217;d read it. Elf sees a parallel with e&#x2011;book publishers&#8217; attempts to ensure that we never, ever share our books with others&nbsp;&mdash; we might as well destroy them completely once we&#8217;re done with&nbsp;them.</p>
<blockquote><p>Read it. Read it again if you want. Download &amp; read it later, on a different device. But <em>don&#8217;t pass it on</em>. As soon as you&#8217;re done with it&nbsp;&mdash; forever-and-truly done, never going to read that book again (and really, how many times am I going to re-read Harlequin romances)&#8230; destroy it. Delete that file, blank that space on the memory card. (emphasis in&nbsp;original)</p></blockquote>
<p>Elf&#8217;s basic point, and it&#8217;s one I can&#8217;t find any flaw in, is: &#8220;Books are social. Ebooks are&nbsp;selfish.&#8221;</p>
<p>In the online version of <cite>Little Brother</cite>, in the section called, &#8220;The Copyright Thing&#8221;, Cory Doctorow writes: &#8220;I recently saw Neil Gaiman give a talk at which someone asked him how he felt about piracy of his books. He said, &#8220;Hands up in the audience if you discovered your favorite writer for free&nbsp;&mdash; because someone loaned you a copy, or because someone gave it to you? Now, hands up if you found your favorite writer by walking into a store and plunking down cash.&#8221; Overwhelmingly, the audience said that they&#8217;d discovered their favorite writers for free, on a loan or as a gift.&#8221; Again, books are social: We don&#8217;t just read them, we also want to <em>share them with&nbsp;others</em>.</p>
<p>E&#x2011;books and readers have many wonderful features, from easily-enlargeable text for people with poor eyesight to a lightweight form factor that makes it so people with weak wrists or arthritis can absorb the latest Neal Stephenson tome without struggling with a door-stopping hardback edition. Oh, and of course it&#8217;s easier to Ctrl&#x2011;F the thing to find text you&#8217;re specifically looking&nbsp;for.</p>
<p>But what are we giving up? And, more importantly, <strong>is there any reason why we <em>have to</em> give it up?</strong> Or are we just getting herded along by circumstances, and forgetting to actually <em>look at where we&#8217;re going</em>, and <em>exert some decision-making willpower</em> of our&nbsp;own?</p>
<p>We have the power to decide what kind of future we want. But we have to stop and think long enough to use it. McGuire and Elf have been doing some thinking, and the points they make are important&nbsp;ones.</p>
]]></content:encoded>
			<wfw:commentRss>http://kagan.mactane.org/blog/2011/09/24/what-are-we-giving-up-with-e-text/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Would an Ideal Portable-Computing UI Look Like?</title>
		<link>http://kagan.mactane.org/blog/2010/02/23/what-would-an-ideal-portable-computing-ui-look-like/</link>
		<comments>http://kagan.mactane.org/blog/2010/02/23/what-would-an-ideal-portable-computing-ui-look-like/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 17:51:53 +0000</pubDate>
		<dc:creator>Kai MacTane</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[mobile computing]]></category>
		<category><![CDATA[Palm Pre]]></category>
		<category><![CDATA[sci-fi]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://kai.mactane.org/blog/?p=194</guid>
		<description><![CDATA[Right now, the question of what you need in a mobile computing platform is most often phrased in terms of &#8220;Do you need a netbook or a full laptop? Or perhaps one of the new high-end smartphones will manage?&#8221; I think the question isn&#8217;t one of capabilities as much as it is a question about [...]]]></description>
			<content:encoded><![CDATA[<p>Right now, the question of what you need in a mobile computing platform is most often phrased in terms of &#8220;Do you need a netbook or a full laptop? Or perhaps one of the new high-end smartphones will manage?&#8221; I think the question isn&#8217;t one of capabilities as much as it is a question about <em>how we access those capabilities</em>.</p>
<p>For some people, the iPhone&#8217;s lack of a physical keyboard is a deal-breaker. For me, the smaller-than-standard keyboard on the average netbook is a powerful disincentive: If I had to use one, it would slow down my interaction with the netbook&nbsp;&mdash; and if I learned to be fluent and productive with the small keyboard, it might mess up my muscle memory for dealing with full-size keyboards on my &#8220;real&#8221; computers. It&#8217;s not a trade-off I&#8217;m willing to make.</p>
<p>The Palm Pr&#275;&#8217;s physical keyboard is tiny. I can only key it with my thumbs, and there&#8217;s no risk of interference with my pre-existing keyboarding skills. Inputting data with it is achingly slow, but offset by the device&#8217;s wonderful portability (it fits into a pocket even easier than an iPhone does). But I can&#8217;t really edit text with it, because there&#8217;s no D-pad to do precise cursor positioning with. Even <a href="http://forums.precentral.net/palm-pre/186259-cursor-control-difficult.html">the Orange+finger-movement trick</a> is balky and awkward, in my experience; if I want to correct a single-letter typo, getting the cursor after the incorrect character so I can backspace and correct it is such an ordeal, it&#8217;s often quicker and easier for me to use Shift+Backspace to delete the entire word and then retype the whole thing.</p>
<p>In effect, even though the phone has the ability to edit text, the interface makes it so difficult that <em>I can&#8217;t use the capability</em>. It might as well not be there. What would a better interface mechanism look like? <span id="more-194"></span></p>
<p>In Charles Stross&#8217; <cite>Accelerando</cite>, the protagonist starts off with a set of glasses that provide him with a constant Net connection and heads-up displays of whatever he desires: maps, email, people&#8217;s vCards, and so on. But Stross (perhaps wisely) doesn&#8217;t give much detail about the glasses&#8217; input mechanism. &#8220;He glances up and grabs a pigeon, crops the shot and squirts it at his weblog to show he&#8217;s arrived.&#8221; How? That part&#8217;s left to the reader&#8217;s imagination. (A very crafty trick on Stross&#8217; part, and one that writers can pull off and user-interface engineers <em>cannot</em>.)</p>
<p>If I want to do with my phone what Stross&#8217; character did, I have to yank it out of my pocket, press the power switch, then make a swiping gesture that tells the phone its attention has been requested by a real human (rather than simply being jostled in a pocket or handbag). But Stross&#8217; protagonist&#8217;s glasses were already powered up and in use, so suppose I were already using my phone and decided I wanted to take a picture of something?</p>
<p>Tap a physical button to escape from whatever app I was already using, then press an on-screen button for the main &#8220;launcher&#8221; feature. Find the &#8220;camera&#8221; icon, tap it, wait for the camera to load. Then I can aim and press another on-screen button to capture the image.</p>
<p>Cropping is pretty much out of the question, although someone <em>could</em> write an app for it. And I actually <em>can</em> update my blog from my phone; it has a WebKit-based browser and enough screen real estate to make writing and posting an entry possible, albeit painful.</p>
<p>Stross&#8217; interface has the luxury of not having to be real, of course. But something that already works as a real-life prototype is the Sixth Sense system, built by Pranav Mistry of MIT&#8217;s Media Lab. It senses the user&#8217;s hands, and <a href="http://www.youtube.com/watch?v=nZ-VjUKAsao&amp;feature=player_embedded#at=198">you can take a picture simply by framing whatever-it-is you want to capture with your fingers and thumbs</a>. (It does a whole lot of other things, too, and I highly recommend the entire video.)</p>
]]></content:encoded>
			<wfw:commentRss>http://kagan.mactane.org/blog/2010/02/23/what-would-an-ideal-portable-computing-ui-look-like/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Back to My Usual Server</title>
		<link>http://kagan.mactane.org/blog/2009/04/18/back-to-my-usual-server/</link>
		<comments>http://kagan.mactane.org/blog/2009/04/18/back-to-my-usual-server/#comments</comments>
		<pubDate>Sun, 19 Apr 2009 04:05:22 +0000</pubDate>
		<dc:creator>Kai MacTane</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[diary]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[source control]]></category>

		<guid isPermaLink="false">http://kai.mactane.org/blog/2009/04/18/back-to-my-usual-server/</guid>
		<description><![CDATA[After a couple of months of temporary hosting with A2 Hosting, I finally have my real server back online, at a colo space in San Jos&#233;. Not that I have any complaints against A2 (heck, I even just gave them a little more Google-juice); they were perfectly servicable. But I&#8217;ve really gotten used to having [...]]]></description>
			<content:encoded><![CDATA[<p>After a couple of months of temporary hosting with <a href="http://a2hosting.com/">A2 Hosting</a>, I finally have my real server back online, at a colo space in San Jos&eacute;. Not that I have any complaints against A2 (heck, I even just gave them a little more Google-juice); they were perfectly servicable. But I&#8217;ve really gotten used to having my own box that I have root on and can do whatever I want with; by comparison, cPanel just isn&#8217;t enough.</p>
<p>Possibly most important&nbsp;&mdash; certainly more important than I would have expected just a few years ago&nbsp;&mdash; is the fact that <em>now I have my SVN repository back</em>. I&#8217;ve recently checked in two months&#8217; worth of code changes. I wound up describing the extreme discontinuity as &#8220;the Spring 2009 Downtime&#8221;, because the first few ideas that drifted through my head just sounded a little too grandiose and overblown.</p>
<p>Still, I&#8217;m reminded of a scene in Joe Haldeman&#8217;s early novel <cite>Mindbridge</cite>. A team of interstellar explorers get sent off to an unknown planet via teleportation technology, wearing fully self-contained environment suits that keep them alive for two weeks. When they&#8217;re teleported back to Earth and a safe enviroment, Haldeman writes: &#8220;they scrambled out [of their suits] to an orgy of backscratching&#8221;.</p>
<p>I know the feeling.</p>
]]></content:encoded>
			<wfw:commentRss>http://kagan.mactane.org/blog/2009/04/18/back-to-my-usual-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

