Yesterday I started reading Cormac McCarthy's The Road (It's a wonderful book, by the way--the kind I would stay up all night reading if I didn't have to take care of my 1-year-old son the following morning). Here is the first paragraph:

When he woke in the woods in the dark and the cold of the night he'd reach out to touch the child sleeping beside him. Nights dark beyond darkness and the days more gray each one than what had gone before. Like the onset of some cold glaucoma dimming away the world. His hand rose and fell softly with each precious breath. He pushed away the plastic tarpaulin and raised himself in the stinking robes and blankets and looked toward the east for any light but there was none. In the dream from which he'd wakened he had wandered in a cave where the child led him by the hand. Their light playing over the wet flowstone walls. Like pilgrims in a fable swallowed up and lost among the inward parts of some granitic beast. Deep stone flues where the water dripped and sang. Tolling in the silence the minutes of the earth and the hours and the days of it and the years without cease. Until they stood in a great stone room where lay a black and ancient lake. And on the far shore a creature that raised its dripping mouth from the rimstone pool and stared into the light with eyes dead white and sightless as the eggs of spiders. It swung its head low over the water as if to take the scent of what it could not see. Crouching there pale and naked and translucent, its alabaster bones cast up in shadow on the rocks behind it. Its bowels, its beating heart. The brain that pulsed in a dull glass bell. It swung its head from side to side and then gave out a low moan and turned and lurched away and loped soundlessly into the dark.

As I read this opening what really stood out to me was the grammatical style, and I couldn't help thinking what kind of comments this book would receive if given to a high school English teacher for an assignment. "Fragment. Fragment. Fragment. Don't needs an apostrophe. Fragment."

When I first started teaching English I thought it was important to strike a balance between the necessary evil of teaching formal grammar and my desire to make language exciting and creative for students, although I wasn't always sure of how to do it. I think that one tactic I settled on was teaching students about using different writing styles for different occasions: what is appropriate for a novel may not be appropriate for an academic paper. I still think this is true, but I've always felt there's more to it than just that.

While reading Cormac McCarthy's writing (this is the first novel of his I've read and now I'm wondering why I waited so long) I've figured out a different reason for teaching grammar. What I've realized is that while McCarthy breaks the rules of formal writing, it is not at all chaotic or disorganized. In fact, I would say that he writes in a very consistent style that has its own consistent set of rules. This kind of writing must be very intentional. I'm sure there's a reason he leaves the apostrophes out of contractions like cant, dont and wont, and I'd love to hear him explain what that reason is.

I think that intentionality is the difference between good writing and bad writing. If a student is going to choose to use sentence fragments, it must be a deliberate choice, which requires knowledge of the formal rules of grammar and a clear purpose for violating them. And above all, grammar should be taught with the understanding that any stylistic choices must be made with the audience's reaction in mind.

I think I'll show my students this passage from The Road next time I teach about sentence fragments in a regular education English classroom.

Last week Apple finally released the iPhone SDK so that developers can create programs that run natively on the iPhone. I downloaded the SDK and installed it. It would be fun to learn some Objective-C and try my hand at making iPhone apps, but web development is my main interest right now. While the iPhone has always been able to run web apps through the mobile version of Safari, the new SDK does include some tools for web developers. Dashcode, which used to just be a tool for making Dashboard widgets, now lets you make iPhone-optimized web applications. It includes most of the UI elements and animations that native apps have, but it's all done in XHTML, CSS and JavaScript.
I used the RSS template in Dashcode to make an iPhone version of my website: personman.com/i. It runs off of my normal RSS feed, but it presents the data in an iPhone-friendly way. All I really had to do was plug my feed url in and then I added my header image and changed some fonts. And the SDK comes with an iPhone simulator, which I used for the screenshot.

The page works in Safari on a computer, too, but if you try to view it Firefox or IE it's going to break badly. The apps that Dashcode creates use some custom JavaScript functions that only work in Safari. Most of them are meant to improve performance or add eye candy. I don't have one yet, but I think the iPhone is a great device. I'm torn about this approach to development, though. It's incredible to have such a small device with these kinds of capabilities. The non-standard browser features like SVG, off-line data API and hardware accelerated animations make it possible to do so much with so little. But making a version of a site that only works in one browser and breaks terribly in all others feels a bit too much like using FrontPage to make a site that only works in IE. The fact that FrontPage sites are disgustingly ugly and iPhone sites are sexy and useful doesn't change the basic fact that it's flouting standards and causing problems down the road. Apple says that they're submitting these features to the web standards boards.

This was a fun experiment and I'll be learning more about it, especially if I finally break down and get an iPhone. Even though there are upsides and downsides to developing for the iPhone, the important fact remains that it has the best mobile browser that I've ever seen. It does a brilliant job of making regular web pages useful on a small screen.