Jeff Duntemann's Contrapositive Diary Rotating Header Image

books

The Google Books Settlement

My miscellaneous low-priority do-it list has gotten mighty long since January, and every so often I set aside some time to knock off a few items. This morning something interesting bubbled up to the top of the stack: Claim my books under the Google Books Settlement. I’ve known about this for quite some time and haven’t had the mental bandwidth to look into it deeply, but having been roused by rowdy dogs this morning a little earlier than I’d like, I sat down here and read the material.

I’m not quite sure what to think. Google is helping to create a registry of old books that are still in copyright but no longer in print. This is a very good thing, and I signed up to support that effort if nothing else. What Google intends to do is create a legal framework for making those old books available as paid ebooks, and give authors (and where publishers still have rights, publishers) a portion of the take. Google has already scanned a great many books, including a few of my own, and if I can pick up a few quarters by buying in to the system, I will. (Alas, I doubt my 1987 work Turbo Pascal Solutions is going to be a hot seller.)

Mostly, I want the problem of orphan books to be finessed, and I want it finessed without Big Media’s copyright lobby shaping it so that it routes all the money to them and leaves the rest of us penniless in the dust. People gripe about Google’s interest in the whole thing–they could make an enormous amount of money here if this thing catches on, and in essence become the planet’s largest publisher–but the idea is sound and Google may be the best that we can do.

If anyone has any interest in this, go to the Google Books Settlement Site and read the sizeable FAQ. I especially encourage any of my author friends who have published books to decide what they think about the whole thing, and either sign in or opt out. Signing up can be done until January 5, 2010, but opting out must be done by May 5, 2009. I’m guessing that popular authors and their heirs will opt out, figuring they may be able to get a better deal somewhere, and the great starving writer masses (who know that there are no deals on their horizon) will sign on. And that’s actually a good thing: The great starving writer masses deserve a way to get whatever scraps may fall from the ebooks publishing table, as the publishing industry generally becomes more and more of a “winner takes all” kind of business.

The framework has not yet been completely created, but it’ll happen over time, and it will be very interesting to see if anything comes of it long-term. I’m watching the whole business closely and will report here from time to time, especially once I finish the Book That Ate 2009.

Cuisine

cooking.jpg

For those who care, I’m 124,266 words in at the moment, shooting for 175,000. Chapter 10 must be submitted before the end of April, and I’m rustier on some of this stuff than I thought.

I recognize that I’m way overdue for writing something profound here, but my head’s still too full of conditional jump instructions. So I’ll punt and offer something less than profound: Whether or not the book cover at left is funny depends heavily on whether or not you have very young children underfoot.

(Couldn’t they have drawn Pooh stirring a pot of spaghetti sauce?)

Odd Lots

  • The United States has overtaken Germany as the world’s lead producer of wind energy, measured in total kilowatts. Way to go–keeping in mind that Germany still beats us all hollow with kilowatts per capita. I’m a big believer in NWS, in that order, and part of the reason N comes before W is that over the past few years, when Carol and I have passed giant wind turbines along I-80 on our way to and from Chicago, they were only turning about a third of the time. Wind energy is great, but it does not stand alone.
  • Small children should be allowed to get dirty as a way of building their immune systems. I was digging in the back yard since before I can remember, and never had much trouble with allergies. There may be a downside to our dirt- and germ-averse culture that has nothing to do with the risk of antibiotic-resistant pathogens. (With Gretchen’s approval, I think I’m going to buy our nieces a couple of garden trowels next Christmas…)
  • Few people today remember that Apple Computer was once a Pascal shop, and had a promo poster in the late 70s incorporating a classic “railroad” diagram of Pascal language syntax. Yes, the 70s really did look like that. (At least it wasn’t all done in Harvest Gold.) Thanks to Paul Santa-Maria for the link. Paul created his own version of the poster in black and white, which I hope he makes available at some point. The Waite Group sold (or gave away; not sure if it was a boom promo) a similar card in the same era, but it’s long since vanished from my collection.
  • Has anyone here ever read any of the Very Short Introduction books from Oxford University Press? Are they useful? I just ordered several, and I’m curious as to the quality of the series. I’ll report here once the books show up and I’ve had a chance to read them. There are many subjects I’m interested in sufficiently to read 150 pages on, but not 600 pages.
  • A German publisher wrote an article claiming that cheaper ebooks will put them out of business. (The article is in German; take what you can from the English summary or if you know the language, click through to the original.) The gist is that there are special costs associated with e-publishing that more than balance the special costs associated with print publishing. My take: If true, it’s only until we get up to speed. (I also think it may be true that many publishers don’t really understand all the forces that bear on how they make their money. Many things lead up to the cash-register’s beep, not all of them obvious.
  • I’m a lot less sanguine about the OLPC than I used to be, but the recent unveiling of future designs intrigues me: The next-gen OLPC will have two displays, and can be held and read portrait-style, like a book. When a keyboard is needed, rotate the device 90, and one of the two displays becomes a keyboard. Very cool, and something like that should be sold worldwide by every electronics retailer. (Their peculiar distribution mechanism will eventually be the end of them.)

Cleaning Up 21-Year-Old Writing

Context changes are expensive, whether you’re a writer or an operating system. That’s why I like long, uninterrupted days to write. Writing in small chunks on large projects never worked well for me; I’d rather pull three ten-hour days than find thirty disjointed hours in the course of a week and waste half of each of them trying to recover my train of thought.

So it’s been with the fourth edition of Assembly Language Step By Step. I’ve spent most of the last four days blasting away at it, and if I haven’t returned to the Carb Wars here, that’s the reason. All in good time.

This is a big project, probably the biggest I’ve attempted since Drive-by Wi-Fi Guide, and it’s likely to be eating my life until June. There’s a great deal of new material to be written, and a lot of concepts to be covered that just weren’t issues under DOS. For example, when you work at the assembly level under Linux, endianness comes into play and needs to be explained, even though 85% of the world’s desktop hardware is little-endian.

That’s actually been fun; as I’ve said many times, the very best way to make sure you understand something is to explain it to somebody else. What’s been humbling is running into writing bad enough to make me wince. Every so often, I have to push back in my chair, heave a deep sigh, and ask myself the purely rhetorical question: “Geez. Did I write that?” (I did. 21 years ago. Practice helps…)

No problem; this is what editors do, though I am very glad that we’re not using typewriters anymore. And unlike certain other projects I’ve worked on, the author in this case takes criticism well.

An Embarrassment of Riches

I’m hard at the rewrite of my assembly book, and in going over the chapters closely I realize that I have a lot to do, significantly more than I thought going in. Parts of this book date back to 1988, and the work as a whole was not organized back then the way I would organize it today. So I’m doing more to it than I thought I would, and although that will make for a better book, it’s also eating more of my time. (Expect a few fewer Contra posts over coming months, and perhaps shorter ones.)

I’ve also been using Ubuntu a lot more than I ordinarily do, since the rewrite finally exiles DOS from the discussion except as a historical footnote. I find myself surfacing for a breath now and then, and realizing, I haven’t been in Windows for almost six hours! Crossover Linux has made this possible, since I have Office 2000 and Visio 2000 installed under Ubuntu now, and don’t have to be bouncing between two machines or two partitions to write code and then write about the code.

In the process, I’ve been using Ubuntu more and at more depth than I ever have before. One thing I’m beginning to appreciate is just how easy it is to get software and keep it current, and just how good the software that’s out there really is. That’s changed in ten years. Back in 1999, in order to run NASM under Red Hat I had to download a tar file full of source, unzip it somewhere, and then recompile the whole damned thing. I had no intention of changing the assembler and would have been more than happy with binaries.

It’s different now. With Ubuntu (and I assume most modern distros) you go up to a software repository through a package manager utility, cruise an enormous list of free packages that are available, and check off the stuff you want. Then you click Apply and stand back: The package manager downloads the package and anything that the package depends on, checking first to see if you’ve got any of the prerequisites installed already. Only the stuff you need comes down, and when the smoke clears you have new apps on your app menu, or new libraries tucked in where they’re supposed to go. (Or both.) Wow.

Ubuntu periodically checks to see if updates are available for anything you have installed, and a couple of clicks brings them down and installs them.

I’m sure that not everything that exists is up there, but what’s up there is extremely impressive. If I allowed myself to get distracted, I’d be playing with Gambas and Boa Constructor rather than writing. The Nemiver debugger front end didn’t exist ten years ago, and it will star in the new edition of Assembly Language Step By Step. Most of all, I want to play with Lazarus (the GUI IDE for Free Pascal) and have to slap my hands periodically, or I’d get nothing else done.

The primary barrier to the adoption of the Linux Desktop is unlearning old habits, followed as a distant second by conversion of existing Windows-centric files. There may have been a third barrier somewhere, but I’ve forgotten what it was. There is certainly no shortage of software to get the jobs done.

Going Into Eclipse

As I mentioned yesterday, my publisher wants me to revise Assembly Language Step By Step over the coming year, for release in early 2010. I had assumed for some time that they considered the book a dead issue, though judging by my royalty statements, it continues to sell. And that's a clue: When the market is bad, publishers get nervous about striking out in entirely new directions with new series and lots of new titles. A handful of books are what they call “evergreens,” because they sell all year, every year, for years and years and years. I think that a lot of evergreen titles are going to be freshened up and reissued in the next few years. The publisher considers my book an evergreen (it was first published, after all, in 1989, and has sold steadily ever since) and the acquisitions editor had done her homework. She wanted DOS to go. She wanted to ditch the CD bound into the book. She wanted more Linux coverage. And if possible, she wanted me to use Ubuntu as the flavor of Linux cited in the book.

I'm cool with all that. I had decided years ago that DOS would be missing from any future editions. I had assumed that I would include coverage of 32-bit Windows console apps, but I'm not welded to that notion, nor to any particular Linux distro. The book is not about Windows, nor about Linux. It needs an OS over which to run the example programs, but which OS is mostly immaterial, so long as it supports the Intel 32-bit flat model. The book is a “front door” introduction to what computers actually are, and how Intel-based machines function under the hood. It's about that waydeepdown place where the software meets the hardware. It is not about how to make API calls nor how to coordinate all the folderol that happens inside large-scale apps.

A lot of people misunderstand the book, and I get gripes all the time about how it “doesn't go far enough” and “doesn't teach the principles of software development.” That's not what it's for, and I don't have the page budget to write enough book to satisfy all my gripers. The format has worked across twenty years and three editions, and I'm sticking with it.

There's still a lot of work to do. Much of the coverage depends on DOS, DOS calls through INT21, and BIOS calls through INT13. All that has to go. I need to explain how the software interrupt mechanism itself works, and for that I'm going to defy the Unix Gods and explain how to use the Linux INT80 call gate. This is heresy, but the mantra that “INT80 calling conventions can change at any time” isn't sufficient reason to keep the secret. I've asked several people to show me an example—even a single example!—of when a Linux INT80 kernel call changed, but so far I've seen nothing. And even if some of the more arcane kernel calls are still evolving, I doubt that the very simple calls have changed at all in many years. Proper warning will be given, but I don't bow before that particular altar anymore.

Alas, if DOS goes, Rob Anderton's excellent NASMIDE programming environment has to go as well, and something else will need to be found to help people load, assemble, link, and run the examples. I've got John E. Davis' text-mode JED editor installed, and in a pinch it will do, but the holy grail for me would be running NASM under Eclipse. Eclipse is a sort of Erector set (ok, a Lego set) for creating platform-independent IDEs in Java. Almost everything beyond the very basics is a plug-in. You can get plug-ins for most modern languages and toolsets, and Eclipse can run anywhere that Java runs. (Of course, your tools must either be in Java or available on the host hardware.) Eclipse itself and nearly all available plug-ins are free and open-source. I've already got it running here on both XP and Ubuntu. All I need is a NASM-oriented assembly language plug-in.

The infuriating thing is that such a plug-in exists, but it comes with no installation documentation, and it does not install the way all other Eclipse plug-ins I've seen install. Eclipse has a clever system in which plug-ins are posted on the Web using a standard format, so that the Eclipse environment can fetch them down and install them automatically, given a URL. I've downloaded the plug-in file and have tried just about everything to get Eclipse to suck it in or even see it. So far, no luck. If you've ever gotten it to install and work, boy, I'd sure love to learn the secret.

I have to scope out some new example programs, write them, and then describe them, and make sure that DOS and segmented Real Mode retreat into a few pages of historical context. It's months of work, even if it becomes my major project (which it will) and knocks most of my lesser projects back into the closet (which it might.) I'm slurping at the firehose right now regarding Eclipse, and have a couple of books on order. It's going to be a long climb, but I've made such climbs before, and they're always good mental exercise. It'll give this book (which I considered a throwaway back in 1989!) another eight or ten years of life. The publisher has always treated me well, and the book paid off my mortgage. What's not to love?

St. Peters, and a Miracle Voice Teacher

It’s been a low-energy and off-my-peak couple of days here for reasons I won’t bore you (or gross you out) with. Had to take a run up to Denver, but mostly I’ve been sitting quietly and reading. I finished a book that I don’t really recommend unless you’re chained to the potty and need to kill time: Basilica by R. A. Scotti is a popular history of the construction of the second St. Peter’s Basilica in Rome, the one that we all know and love, which supports the largest church dome in the world. The book is competently written, but it’s a little thin on details of the construction itself. Ms. Scotti is much more interested in politics and personalities, and in truth I did learn a lot about Bramante, Michaelangelo, Raphael, and Bernini (and more than a few popes) that I didn’t know before. But she has no good head for architecture, and does not define any terms. I kept flipping into a wonderful DK book called The Visual Dictionary of Buildings to clarify certain elements of church architecture. Now that book I recommend, especially if you’re a writer trying to set a scene in a complicated building and aren’t entirely sure what an oculus is. (Or—quick, now!—define a “spandrel”.) There are some factual errors in Basilica, one of the worst of which suggests that poured concrete was used in some places in St. Peter’s. Not so—poured concrete was an ancient technology that was lost after Imperial Rome came apart and was not recovered until the 19th Century, or pretty close to it. St. Peter’s was built almost entirely of mortared masonry and sculpted stone.

If you’re interested in the peculiarities of St. Peter’s Basilica, a better book is The Bones of St. Peter by John Evangelist Walsh, which speaks of the excavations under the main altar just before WWII. The Basilica was built over a Roman graveyard, and there was a lot of fascinating stuff under the floors. More about the Shroud of Turin than about the Basilica is Holy Faces, Secret Places by Ian Wilson, of which I reread a considerable chunk. However, Wilson speaks of the countless weird little crannies in the Vatican complex, in which a lot of interesting things, and not only relics, may be hiding. Secrets are not good in religion for many reasons, but mostly because secrets are a power thing, and power corrupts spiritual organizations mortally. (See Encountering Mary by Sandra Zimdars-Swartz for a good discussion of this problem.) Wilson is a marvelously engaging writer, and potty reading doesn’t get a whole lot better.

I also reread several sections in Peter Ochiogrosso’s fascinating 1987 book Once a Catholic, in which a number of famous Catholics and (mostly) former Catholics explain what sorts of marks their Catholic upbringing left on them. The book is not explicitly about the gulf between Tridentine (i.e., Latin) Catholicism and Vatican II Catholicism, but the demographics of the people the author chose to interview almost guarantees it. Like them, I grew up Tridentine, and like them, I know what we lost, and why. (Not all that was lost was good; in fact, a good deal of what we lost was desperately in need of losing.) The book is secular in approach and intent, and does not preach, in either direction. It’s a character study, of real characters. (One of them is George Carlin.) Highly recommended, and I think I’ve spoken of it here before.

All these books but Basilica are currently out of print, but cheap on the used market. Reading them was research for a current project of mine—Old Catholics. (Nothing makes you a better writer than simply reading, and reading a lot.)

Finally, I’ll throw out an idea I had yesterday, for an invention I wish someone would get to work on. I want something I might charactize as a Miracle Voice Teacher. I want a program that will put a musical score on the PC screen and listen to me try to sing it. The program should average the frequencies that come in from the mic and put a line above or below a note in the score, telling me whether I’m high or low. It should have a metronome, and the ability to play the score as MIDI. It should be able to record what I sing and play it back for me, showing me on the screen where I botched the melody.

And if that’s possible, then the program should be able to teach me how to harmonize, by isolating one of the melodic lines and allowing me to sing it, and then gradually adding in the other lines in the headphones while I try to stick with my own line and not get confused. Scarily, such a thing would allow me to sing four part harmony…with myself. The world may not be quite ready for that, but at this juncture I think I am. I went looking for the product and didn’t find it, but if you know of something along those lines, I’d like to hear about it.

The Risks of Quirky English

As I've mentioned here a time or two, I've been gradually recasting my 1993 book Borland Pascal 7 From Square One for the current release of FreePascal. It's turned out to be a larger project than I had expected for a number of reasons, some of them humbling (I was not as good a writer in 1984 as I am today) and some completely unexpected. The one that came out of left field stems from the fact that Pascal isn't used in the US that much anymore. Most of the audience for the new book is in Continental Europe, and while most of them understand English, they understand correct, formal, university-taught English.

Not slangy, quirky, down-home, Jeff Duntemann feet-up-on-the-cracker-barrel English.

This became clear some time back when I posted the first few chapters for FreePascal users to look at. I got a few emails with detailed critique (for which I am extremely grateful) and there was a certain amount of puzzlement about some of the language. A few of the things that puzzled my European friends were not a surprise:

  • QBit stretches and climbs on my chest, wagging furiously as though to say, “Hey, guy, tempus is fugiting. Shake it!”
  • Ya gotta have a plan.
  • …and write the plan in German, to boot.
  • …cats are pets, not hors d'oerves on the hoof.

But some were. The expression “to run errands” is not universally understood there. Nor is the word “shack.” (I changed it to “shed.”) I want very much for the book to be accessible to those who are using Pascal the most, and that's a new kind of challenge for me: Writing plain English without resorting to clever coinages and Americanisms.

Alas, I'm not always aware of it when I'm using Americanisms. (I should find a book for English-speakers traveling here, just as there are books on British English for those of us who visit the UK.) There are other problems: Europeans are not intuitive with Fahrenheit temperatures, any more than we're intuitive with Celsius here. I mentioned in the book that it hit 123° in Scottsdale once in the summer of 1996, and although my European friends know that that's hot, when I translate it to Celsius—50°—they gasp. We were gasping too—Keith and I had to shut the Coriolis offices down because the air conditioners were losing the race. Solution: Put temps in Celsius. Americans know damned well how hot it is in Scottsdale. (As I left in 2002, it seemed like most of them had already moved there.)

It's a two-edged sword. I like writing the way I talk, and for those who haven't met me, well, I talk the way I write. It's easy. On the other hand, having worked my way through the first hundred-odd pages of the new book, straightening out my language quirks, I find that it now reads very well. It doesn't sound quite as much like me, but that's OK. The idea is to keep Pascal alive, wherever and however it is to be done. Writing for the world—and not strictly for us American barbarians—is a useful skill and good discipline. If I stick with Pascal and Delphi, which I have every intention of doing, you're likely to see more of it in the future.

Tabletop Fluoroscopy for Boys, Circa 1913

It took a few minutes of flipping through some books in my workshop, but I eventually found what I remembered: That one of my “boys” books contained a description of a tabletop X-ray setup. The book in question is The Boy Electrician, the first volume of many from Alfred Morgan, who later wrote The Boys' First Book of Radio and Electronics and its three sequels, all of which loomed large in my tinkersome youth. The Boy Electrician was originally published in 1913 and is now in the public domain. The 1913 edition has been reprinted by Lindsay Books and I consider it worth having. There was a significant revision in 1943 that added chapters on radio and a few other things, and as best I can tell, the copyright on that edition was not renewed and it too is now in the public domain. A 40 MB PDF of the 1943 edition is here.

The Boy Electrician explains that “it is possible to obtain small X-ray tubes that will operate satisfactorily on an inch and one half spark coil.” This does not refer to the coil's dimensions; it means a coil capable of generating a spark an inch and a half long. He goes on to say that X-ray tubes cost about four and a half dollars each (albeit 1913 dollars) and may be obtained from laboratory supply houses. Hookup is fairly simple, with the spark coil driven by four of those wonderfully gutsy #6 dry cells with the huge carbon rod running down the middle. The drawing of the setup is shown below:

Morgan explains that you can either view images directly with a fluoroscope or expose ordinary photographic plates by placing an object to be X-rayed between the tube and the plate and leaving it there for fifteen minutes. This includes things like purses, mice, or…your hand. If you have the money, he also explains that a hand-held fluoroscope may be constructed by simply coating a sheet of white paper with crystals of platinum barium cyanide. It looks like the fluoroscope screen is used by basically staring at the X-ray tube with the object to be X-rayed between the tube and the paper screen.

It would be interesting to know just how many boys bought the tube and tried to make it work; though given that $4.50 in 1913 would be about $100 today, I doubt it was many. Nor do I know how toxic platinum barium cyanide is, but I'm guessing a little more than iron filings. (On the other hand, my 1962 chemistry set contained a little bottle of sodium ferrocyanide, which sounds much worse than it actually is.)

I remember taking The Boy Electrician out of the Chicago Public Library when I was 12 or so and pondering the X-ray project. What stopped me wasn't any fear of X-rays themselves, but concern that the whomping big spark coil would wipe out TV reception for a quarter mile in every direction and get me in trouble with the FCC. My friend Art had an old Model T ignition coil, and we could hear it sizzling on Art's transistor radio for half a block. The project had to be safe; I mean, the book was in the juvenile section of the library…

We knew less about a lot of things in 1913; X-rays were in some respects the least of it. But the hazard is significant, if not as bloodcurdling as luddites specializing in radiation insist. People used to self-treat insomnia by inhaling chloroform; well-known Victorian British scientist Edmund Gurney died by falling asleep with a chloroform-soaked cloth next to his nose. We know more now, and understand the precautions a great deal better, which has led to an escalation of conern that (untempered by any grasp of statistics or risk evaluation) quickly descends to rank superstition. One has to wonder how much knowledge isn't obtained these days simply because people are afraid of small but nonzero hazards. Panic over traces of phthalates—then heedlessly drive fifty miles to a football game with a car full of kids. It's the modern way of life.

Borders Focuses on Impulse

An article from yesterday's Wall Street Journal basically confirms Borders' ceding some territory in their war with online booksellers both used and new. (And “gently used,” i.e., read once and resold online.) Borders has begun a new shelving strategy in which a great many more books are shelved face-out rather than spine-out. To make room for all those additional face-outs, the chain will be reducing the numbers of titles carried per store by 5%-10%. For the larger stores, that will mean 4,000-9,000 fewer titles carried.

The doofy marketing consultant quoted in the article tells us that “People don't want choice, they want what they want.” I hope Borders didn't pay him too much, because that's an abysmally stupid statement. People who want what they want order online at a steep discount. People who shop at Borders (and other large bookstores) often don't know what they want—which is precisely why Borders is changing to face-outs on their shelves. When I know precisely what book I want, I order online, in part because I'm contrarian in my book tastes, and in part because I don't like to drive when I don't need to. I go to bookstores these days mostly when I have to hit the mall for something else. (My own experience shows that buying shoes online is an exercise in futility.) On those occasions I budget some time for Borders or B&N, specifically to buy a few titles on impulse. Impulse will be easier now. Serendipity has value, and prowling bookstore aisles can broaden one's tastes. (Ordering only what one wants tends to narrow one's tastes, just like hanging out only with people like oneself tends to create a social circle of people a great deal like oneself.)

For impulse buying, covers can matter. A big bold title and interesting graphic make it more likely that an aisle-stroller will stop and pick the book up, which is the big win in any kind of merchandising. It may take publishers a little while to realize that their covers may actually catch the eye of impulse buyers now. We might hope for better covers, or—gasp!—better back-cover or dust-jacket summaries.

I expect there to be a lot of bitching and moaning about this, but it's actually a wise decision on Borders' part. They're emphasizing one of the few facets of bookselling where they have an edge over online merchants, and thus helping guarantee that they remain in business. And from an author's standpoint, they're leveling the customer attention field a little: If you can get into Borders at all, you have a decent chance now of being face-out. One of the guerilla tactics of small publishers used to be sending junior staffers (often attractive young women) to stores to pretend to be browsers, picking up a spine-out title published by their employers, flipping through it for a second or two, then slapping it back on the shelf atop a face-out title fielded by a competitor. I don't know how well this worked. I do know that certain enthusiastic young swirlies (as Coriolis staff started to call themselves at some point) spent an insane amount of time at this. Now there'll be less cause to do it, and I'm good with that. If I want to buy The Catholic Experience of Small Christian Communities, I'll order it online. If I just want to surprise myself, well, hey—I'll go to Borders.