Skip to content

Apple

An odd thing happened today…

Macworld logoAnd that odd thing is this: I'm now an iPhone owner. As of yesterday, I had no plans to be anywhere near an Apple or AT&T store today. But that all changed when Macworld asked me to stand in line, buy a phone, and then mail to the corporate office--they wanted to make sure they had several phones in hand for review next week.

iphoneI detailed my camp-out experiences in this blog entry on macworld.com, along with this afternoon update.

Shortly after that last update was published is when my day got really surprising: Macworld asked me to buy two phones, but just send one in their direction--I was to keep one and use it myself, replacing my Treo. Wow. I was quite surprised, to say the least. You see, I didn't even really want a first-generation iPhone; it's missing many things that I'm used to on the Treo. But I guess now I get to see if that's really true, and to write about just how well, or not well, the iPhone works for me. As I have time with the iPhone, my write ups--covering the good and bad of the experience--will appear on Macworld's new iPhone Central pages (and probably on macworld.com, too).

The iPhone is now activated, and it's busy synching all my content. I'll post links here to anything that winds up on Macworld, in case you're contemplating an iPhone of your own.



Apple’s disappointing iPhone message

Macworld logoOne of the biggest questions surrounding the iPhone since its January preview was whether developers outside of Apple would be able to create software that would run on the phone.

And just 18 days before the iPhone's June 29 release, Steve Jobs stood on stage at the Worldwide Developers Conference and told software makers that Apple had found an answer: a 'sweet' way to support outside iPhone development.

Unfortunately, if you're thinking that Apple really addressed third-party development in Steve Jobs's keynote, you'd be wrong. While many people—including myself—have clamored for support for widgets and applications, Monday's announcement actually did nothing at all to address either issue. Instead, it told developers that since Safari on the iPhone is a full-fledged web browser, they can use Ajax and CSS to make nice, pretty Web-based applications.

Read my Macworld blog entry, Apple's disappointing iPhone message, for the rest of the story...



A different kind of paging…

It's Sunday morning as I sit here in this San Francisco airport café, having just arrived on my flight from Portland for this week's WWDC. The flight itself was fine--the air was smooth, the plane was lightly loaded, and I had an entire row to myself. Without being in first class, it just doesn't get much better than that!

However, just before we pushed back from the gate in Portland, I heard this on the plane's PA system: "Rob Griffiths, please press your flight attendant call button." Uh oh. Talk about a quick way to elevate one's heart rate--nothing like an on-board page to accomplish that! A sampling of thoughts that ran through my head: "Uh oh, what happened to one of our kids!?" ... "I bet I left something at home, like my luggage, and my wife is calling to let me know" ... "They figured out that their online check-in tool shouldn't have let me move from the cheap seats up into Economy Plus?" [I was able to jump from row 22 to row 8 without any trouble] ... "Was there something in my carry-ons that they've just now discovered to be dangerous?" ... "Someone saw me taking pictures of the airplanes from the concourse windows and called security" ... "I always wondered what happens when someone is asked to press their flight attendant call button; looks like I get to find out!"

After all that (and more) had run through my head for a couple of minutes, the flight attendant showed up and simply said: "Ah, thank you--we just wanted to make sure you were on the plane. Didn't want to leave without you!" Whew, no emergency, no trouble. But then I began to wonder...how come they didn't already know I was on the plane? After all, I had handed them my boarding pass at the top of the jetway, they had scanned it through their boarding system, and I heard the thing go "beep."

The only thing I can think of is that by jumping from steerage into Economy Plus (or whatever my airline calls it), I somehow confused their system. Perhaps the gate agent did something special to let me claim my 'upgraded' seat--the flight was quite empty after all--and that somehow 'lost' me in the system? Whatever the reason, it was just a bit disconcerting to find myself 'lost' in an airplane despite having had my boarding pass scanned prior to boarding!

In any event, I'm here now, and have a free day to explore the city and its surroundings and take some pictures with the new camera. Tomorrow things get busy, with the (public) keynote talk in the morning and then a number of "state of the union" presentations in the afternoon, and a reception in the evening. I'm hoping that there are at least one or two real 'wow' secret features revealed in Leopard, as I'm not overly impressed at the moment (based on the features shown on Apple's OS X pages). We'll know one way or the other in about 24 hours!



Vacuous Vista versioning

Macworld logoWhile thinking about the upcoming release of 10.5, aka Leopard, I realized that Apple has yet one more advantage over Microsoft: simpler choices for the consumer who is contemplating an OS purchase. I compared Vista and OS X versions in this May Editor's Notes writeup on Macworld. As a friend noted, it's almost like Microsoft is making it hard to purchase Vista, given the differing versions one must choose between.



Shopping (or not) at the Apple Online Store

Macworld logoI wrote this piece back in May, when the Apple Store was down for about four hours, and for what? To release some very modest speed bumps to the MacBook line. I can't think of any other major online vendor that takes their store down when they add new products, which is what inspired me to write the piece.



When updates overlap

On Thursday of this week, we had two interesting software update announcements:

  1. Microsoft released an update to Vista that fixes a problem with Apple's iPod corrupting when ejected.
  2. Apple released the Boot Camp 1.2 beta, which adds support for Microsoft Vista (among other new improvements).

So on the same day, Microsoft patched their OS to prevent Apple's iPods from corrupting on disconnect, and Apple released an update to enable its customers to use Microsoft's Vista on Intel-powered Macs.

I just found it somewhat humorous that both Microsoft and Apple released patches to fix issues with the other's products on the same day...and I'm thrilled that it happened, as it shows that companies realize how important it is for our hardware and software to play well with others. (My own Vista upgrade is in the mail, so I'll see how well the updated Boot Camp works in the near future.)



The limits of Apple’s warranty

Macworld logoLast week, I had an issue with my MacBook Pro--the backlight went out. The machine is about 110 days old, so it's just over Apple's 90-day limit for phone tech support. I think it's pretty outrageous that a $2,500+ machine comes with only 90-days of phone support for hardware issues, and I shared my thoughts on the subject in an opinion piece for Macworld on Friday.

I really think that Apple is lagging with their policies, but some of the feedback to the opinion piece has prompted me to look into it further. I'm not sure if anything will become of it, but it's my plan to look into the bigger names in the PC world and compare their policies with Apple's for similar gear. Just for fun, I'm also planning to look at the major home electronics manufacturers, at least those who sell gear in a similar price range as something like the MacBook Pro.

If anything like an article comes of my great plans, I'll post a follow-up...



An Office 2008 VBA to AppleScript helper

Macworld logoA while back, I wrote about what I thought of Microsoft's decision to drop Visual Basic for Applications (VBA) from the next version of Office. In short, I think it's a short-sighted and stupid decision. Apparently my thoughts had no influence on the folks in Redmond (shocking, I know!), as Office 2008 is set to ship without any form of VBA support.

But it will have AppleScript support, and the fine folks at MacTECH were kind enough to send me a preview copy of their upcoming 150+ page guide to switching from VBA to AppleScript. I wrote a brief preview of this guide for Macworld last week. If you're a serious VBA scripter looking to make the move to AppleScripts, this looks to be a must-have guide. And thanks to some Microsoft support, you can buy it and six-month subscription to MacTECH for all of $10 or so. More info can be found in the link in the Macworld article.



Technology purchasing: A 10 year retrospective

I've been playing around with technology for longer than I care to remember--I blame my father for bringing home that first Commodore PET way back in 1979. Ever since then, it seems, I've had this unhealthy fascination for pretty much everything on the bleeding edge of technology. I clearly wouldn't have my current job without this interest in technology, so I guess I'm quite thankful that things worked out the way they did.

However, such a hobby does have its costs--literally. I was cleaning out our cabinets the other day, and came across my binder of technology receipts. This is where I keep the receipts for any "substantial" hardware or software purchases, and it tends to be something of a roach motel for receipts: they check in, but they never check out.

So I thought I'd take some time and cull the receipts for things I no longer own. Going through the binder is quite the revelation--both on how much I spent on technology (hey, I was young, single, and careless...now I'm just careless!), but on how much the technology itself actually cost. I scanned a few bits from some of the more interesting receipts (click any receipt for a larger version).

Read on for a walk down memory lane...followed by a look at what those items would cost in today's dollars, as well as what you could get for that some money today!

[continue reading…]



Recent Macworld articles cross-posted

Macworld logoDespite my promise to stay on top of my Macworld postings, I haven't done all that well at doing so. This morning, I posted a small flurry of Macworld stories, covering the last few months' editorial pieces. Since I filed them correctly according to date, you won't see them in the RSS (I don't think?), so here are some links to the Macworld pieces, along with a short synopsis of each article:

  • Feb 28th: Don't leave the Windows open: A real-world example of what can happen to a seemingly reasonably well defended Windows XP Pro installation (as installed under Parallels on my Mac Pro). [robservatory link]
  • Feb 9th: On meaningless hyperlink graphics: I rant about Snap's "Preview Anywhere" technology, which pops-up an (unrequested!) miniature preview icon of the page you'll visit when you click a link. Ugh. [robservatory link]
  • Jan 12th: Ten iPhone suggestions: As cool as I think the iPhone will be, I probably won't be buying one. The Treo I have is so much more than a phone that I can't see losing those capabilities by switching to the iPhone. If Apple were to implement at least the majority of my ten suggestions, though, then I'd switch in a heartbeat! [robservatory link]
  • Jan 3rd: Reading between Apple’s lines: I wrote this piece after Apple's homepage changed to read "The first 30 years were just the beginning" the week before Macworld Expo. In the article, I predicted the contents of the keynote speech. Though nearly everything I wrote turned out to be wrong, I got the iPhone's general concept right, though my comment of though not even Steve can really get away with a one-button phone--can he? turned out to be exactly what he did get away with! [robservatory link]

Just so I can finish with another promise to be broken, I really will try to stay more on top of these posts from now on! :)