I’m generally not one to beat a dead horse, and although the recent debacle (full details below) with the misplaced iPhone prototype quickly achieved ‘time to make some glue’ status, this clip is worth posting. By the end I’m left asking the same question I’ve been asking for quite some time: “Really Apple…really?”

By the way, if you’re interested in reading up on the complete story, Gizmodo has provided the following collection of links. For the record, I think Gizmodo could have handled things more appropriately and professionally, but I’m not all that surprised considering their less than mature track record.

• All the details about the next iPhone including a dissection
• How Apple conceals prototype iPhones
• How Apple lost the next iPhone
• How Apple missed chances to get the device back
• Conspiracy theorists: Why Apple didn’t leak the iPhone to us
• Why it’s not about the iPhone
• And finally, how Apple asked to get their phone back

tl;dr at the bottom …

Background:

Adobe has made moves to allow Flash applications to compile to executable applications for desktop use through the AIR runtime. Adobe announced that Flash CS5 will allow flash applications to compile through AIR to iPhone applications. This would expose worlds of nice API and functionality and ease of deployment to the iPhone stores.

Then, Apple updates its Terms of Service in 4.0 to say that “Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited.” Essentially, this term bars Flash from compiling to the iPhone. This would also theoretically ban other systems like Unity3D and Ston3D from doing the same thing, but the current forecast is that those applications will likely be allowed through while Flash is being targeted.

(more…)

Sorry, I had to. Source of the image and other related humor can be found at jezebel.com

If you guys are interested, Engadget is doing a live blog of today’s Apple event. It’s all but certain that their new tablet will be announced today, which a lot of people have been waiting patiently for. Other speculation suggests that the iPhone will be coming to Verizon today, as well as a new version of iLive. Click on the image above or this link to watch (read?) along.

It’s been almost a year since I made this post regarding Windows 7 (and let me be the first to admit that in retrospect that comes off really Apple fanboy-ish, and after using Win7 @ work for the last month or so, it’s actually a terrific update to XP & Vista and a great OS in its own right), but this is just too damn familiar to another OS-vendor-specific store…

I understand that grand opening store excitement isn’t a copyrighted feature of ANY retail store, but come on…

So I was having some issues upgrading my iPhone to OS 3.0.1, which is something anyone with an iPhone should do, as the vulnerability it fixes is seriously scary(first link is news story, second is link to white paper PDF, consider yourself warned), and my cat knocked the iPhone off a table, thereby disconnecting the USB cable during the upgrade.

I wasn’t too freaked out – I back up daily – but I was curious to see how the installer handles situations like this, which led me to my laptop’s syslog/Console, and this hilarious gem:

Aug  2 13:57:57 wootbook2 [0x0-0x23023].com.apple.iTunes[371]: MobileDevice: _MobileDeviceConnect_locked: This is not the droid you’re looking for (is actually com.apple.mobile.restored). Move along, move along.

I’m glad to see nerdy Star Wars jokes/easter eggs can still pass through a major tech company’s QA department.

That’s an interesting angle to be getting that type of reflection, don’t you think?