Chicago Sun Times article on Google Wave. It gives an example on how it could potentially work in the Sun Times environment.
Take this very column that I’m writing. Moving thoughts from my head to your eyeballs requires three or four different communications systems. I write the column here in my word processor (1). I email it to an editor (2). He or she makes some changes and if they’re big enough, I get a phone call or a separate email and we talk them over as I make changes (3). It then goes from my editor’s desk to the Sun-Times’ webserver and the mysterious part of the operation that publishes it on paper (4).
No, here’s how this column would be produced using Wave:
I have a browser window open that looks almost identical to my Google Mail window. I have an “inbox” of fresh Waves (well, if you must think of them as “messages” then go ahead … but I want my objection noted).
Just as with a conventional Inbox, the newest Waves are at the top. Waves with unread contents are highlighted in bold.
I click a button and create a new Wave. An empty editing pane opens on the side of the window, looking almost exactly like a new email message.
But it’s a rich-text editor that supports media and fancy formatting. I write my column. When I’m finally ready to give it to my editor — or at least ready for him to stop worrying that I’m only an hour from deadline and I still haven’t filed yet — I quietly drag his icon into the Wave.
Over at the Sun-Times, the Wave of this column appears in my editor’s Inbox, highlighted in bold. He clicks it to take a look.
Oh, damn. Technically, the Google Wave demo is only 80 minutes, not 90. I should have caught that error.