Meeting Tip: Learning Names | Gurno.com

As someone who suffers from frequent encoding errors and buffer overflows, I love Adam's idea to start a meeting by mapping the name and location of each attendant, along with their title, etc. Adam writes:

Step 1 - Reconnoiter

Draw a quick map of the table/layout of the meeting. Place yourself on it, to give yourself a reference point.

Step 2: The Combatants

As people introduce themselves around the table, fill them in. If you feel last names are necessary add those too, but don't do it at the expense of writing down someone else's name. You can guess at the last names later. If you miss one, leave it blank and fill it in as soon as you can - if someone else refers to them, etc, etc.

A few more of my MacBreak segments from the Macworld Expo floor are now available for download:

• MacBreak 51 Macworld 2007: The Omni Group - (MOV) - 8:03 - "Merlin chats with Ken Case from the Omni Group about their products and the application development possibilities for the iPhone."
• MacBreak 50 Macworld 2007: MacTank - (MOV) - 07:44 - "Merlin chats with the developers of MailTank and MailTemplate."
• MacBreak 49 Macworld 2007: AppZapper, Pzziz and Cha-Ching - (MOV) - 8:58 - "Leo and Merlin continue their tour of 'Tiny Town', visiting with the makers of Cha-Ching, Pzziz and AppZapper."
• MacBreak Macworld 2007: Flip4Mac - (MOV) - 5:59 - "Leo and Merlin chat with the makers of the Flip4Mac suite of digital media tools."

More episodes coming later today. Never miss an episode of MacBreak by subscribing for free.

Two recent articles in the New York Times would seem to put to rest -- at least for the foreseeable future -- any hopes or speculation that the new iPhone will be allowed (nb: I did not say able) to run third-party OS X applications (previously: 43F Podcast: Snell & Gruber on iPhone applications and Let OS X developers at the iPhone. Please.)

Regrettably, the word on this one comes directly from the Steve's mouth (2007-01-12):

“We define everything that is on the phone,” he said. “You don’t want your phone to be like a PC. The last thing you want is to have loaded three apps on your phone and then you go to make a call and it doesn’t work anymore. These are more like iPods than they are like computers.”

The iPhone model, he insisted, would not look like the rest of the wireless industry.

“These are devices that need to work, and you can’t do that if you load any software on them,” he said. “That doesn’t mean there’s not going to be software to buy that you can load on them coming from us. It doesn’t mean we have to write it all, but it means it has to be more of a controlled environment.”

David Pogue's seemingly exhaustive iPhone FAQ also underscores what we'd been hearing via these drams of dolor (2007-01-11):

Can it run Mac OS X programs? –No.

Can I add new programs to it? –No. Apple wants to control the look and feel and behavior of every aspect of the phone.

Well, there you go. Apple appears to be on the path to providing its iPhone customers with a pantry full of excruciatingly beautiful crockery and flatware that may never be set down for chow. (But you can bet we'll always know it's there -- even while we're eating takeout with our assigned spoons).

Spectators at the iPhone Display
Originally uploaded by x180.

Wonderful photo by Duncan.

Sixfoot6 Archives: 30 Things the iPhone Could Do That You Haven't Thought of Yet

Ryan's list contains a lot of the tear-inducingly sexy fantasies that were going through my own mind on Tuesday morning when we all heard that the iPhone was going to run OS X.

Like a lot of my friends, I (probably naively) took the announcement to mean that, as on my own Mac, I'd be able to install Cocoa applications built to take advantage of announced features like WebKit, Core Animation, and so on. Sure, given the foreseeable hardware limitations, these wouldn't be the exact applications that we're each running on our MacBooks today, but, hell, I'd take "OmniOutliner Mobile" or "iTerm Lite" or "Textmate for iPhone" in a heartbeat. No question.

Yesterday morning, though, I started to hear rumbles about the "inability for users to install additional applications of their choosing." And then later, after Brian from Gizmodo got a hands-on demo along with a sit-down with official Apple honchos, he noted...

It isn't OS X proper, as you'd expect. And like an iPod, it won't be an open system that people can develop for. Remember, this is both an iPod and a Phone.

...and I died a little inside.