After thinking about it for a while (and reading other’s reactions around the web), it’s starting to make a little more sense… The iPhone (and, truth be told, the AppleTV) are the next outlets for OS X. I’m almost positive (as are others) that the next iteration of the OS will have a resolution independent scaling engine for the main UI elements. This is directly useful in the iPhone, since it’s display has a pixel density almost 4 times that of a standard computer LCD screen. Plus Core Animation. Plus a host of other things at the core of the OS. So it makes sense that the Leopard team would be working feverishly on the iPhone OS as well. It’s two strains of the same thing.
There’s an old axiom in computer science that states “adding developers to a late software project only makes it later.” (this applies to more than just software, but for that particular discipline, it’s acutely true). However, in this case, people weren’t added to a wholly different product. Their focus was just expanded to include a larger target platform space.
Have you noticed that there’s room for 5 more icons on the main iPhone screen? Do you think those “secret” features that haven’t been announced for Leopard are only for the desktop version of the OS? What if one of those secret features was the iPhone itself?
Something tells me that this will just make the iPhone better. And that’s a good thing. I’m still curious what it’s going to do for the Pro Apps, though. I’ll find out in Vegas in a couple of days.
Apple delays Leopard (Mac OS X 10.5) until October 2007.
Apple Statement
iPhone has already passed several of its required certification tests and is on schedule to ship in late June as planned. We canâ??t wait until customers get their hands (and fingers) on it and experience what a revolutionary and magical product it is. However, iPhone contains the most sophisticated software ever shipped on a mobile device, and finishing it on time has not come without a price â?? we had to borrow some key software engineering and QA resources from our Mac OS X team, and as a result we will not be able to release Leopard at our Worldwide Developers Conference in early June as planned. While Leopard’s features will be complete by then, we cannot deliver the quality release that we and our customers expect from us. We now plan to show our developers a near final version of Leopard at the conference, give them a beta copy to take home so they can do their final testing, and ship Leopard in October. We think it will be well worth the wait. Life often presents tradeoffs, and in this case we’re sure we’ve made the right ones. [Apr 12, 2007]
Wow. Bummer. Don’t get me wrong, I’m drooling for an iPhone as much as the next guy, but not at the expense of Leopard. The thing I’m curious about is how this shakes other things up. Like Final Cut Pro 6, for example. Guess I’ll find out about that on Sunday at NAB.
So, here’s a little story: I ordered an Apple TV the moment the Apple store came back on-line after Steve Jobs’ MacWorld keynote back in January. I was pumped. Here was the media access device for my home network and big screen TV that I had been looking for for years. And it would be shipping in February. Cool.
Then February came and I got a nice little email from Apple saying that they really needed a couple more weeks to make things perfect. So it wouldn’t be shipping until March. Well, OK. I can understand that.
Then the middle of March came and went and no ship notice from Apple. Getting a little nervous, I went back thru the specs that Apple had published on the device, as well as several tech blogs that had been speculating and previewing it. And finally I decided that it just might not do everything I really wanted it to do. So, three days before it finally shipped, I cancelled my order.
Fast forward about three weeks to today. As part of our monthly Final Cut Pro User’s Group meeting, I’ve been called upon to review the device and demonstrate it for the group. So a buddy of mine drops his brand new AppleTV off to me last night and I spent a few hours playing with it. Here’s my review.
It’s pretty cool. But, it’s version 1.0.
OK, first, what is it? The easiest way to explain what AppleTV is is this: it’s an iPod for your TV. It behaves almost exactly like an iPod with respect to it’s interaction with and reliance upon iTunes. It shows up in iTunes as a device, just like an iPod. The preference panels are almost identical, allowing you to select what to sync with it, and it has an internal hard drive that caches the synced content, just like an iPod. The only real difference is it can stream from other iTunes machines on the network.
Even the unboxing was remarkably similar to the iPod experience. The package is the same slipcase design that the new iPods ship in, an unfolding container in a sleeve. The packaging is distinctively Apple. Clean, elegant, efficient, inviting. “Designed by Apple, Inc. in California.” The whole schtick. In the box is the unit itself (a little lighter than I expected), a power cord, the “gum package” Apple remote, and a sleeve of thin manuals. No fluff. Just what one has come to expect from modern Apple packaging.
After peeling the cellophane wrapping off of the unit and remote, I unplugged the HDMI cable from my HD-DVD player and plugged it into the AppleTV, and then plugged the power cord in. No on/off switch. I flipped my TV to the second HDMI input and the Apple logo appeared on the screen.
Once of the touches that makes Apple products distinctively Apple is the fit and finish of the user experience. AppleTV lives up to that expectation (for the most part, more on that later). Instead of jarring visuals that blink on and off, the screen is very clean and elegant. Transitions from one screen to the next are dissolves. The remote is simple and works just as you’d expect. Holding the up or down button down will scroll quickly thru lists, picking up speed as it goes. But I never seemed to overshoot what I was aiming for. They really seemed to spend some time and effort timing the interface and navigation. It felt very natural.

Setup was a breeze. I intentionally noted the time so I could see how long it would take to get things going. I didn’t need to. It took 3 minutes. After showing the Apple logo for a few seconds, the screen faded and then showed me a list of the wireless networks that the unit could find (6 in my case). I selected my network, and the unit let me know that the network was a closed wireless network, and gave me a virtual keyboard on the screen where I could “type” the password (upper- and lowercase, numbers and symbols). After a couple of tries at remembering my password it immediately attached to the network and found the machines I had on that had iTunes running.
The next screen showed a 5 digit code. Looking at my notebook’s iTunes screen, I noticed that the AppleTV had appeared in my device list on the left with a small message “click to setup”. Clicking on it AppleTV item in the list, I was immediately asked for the 5 digit code from the screen. After entering the code, the system informed me that setup was complete and ran the AppleTV intro video (very slick, reminded me of the TiVo setup complete movie).
My iTunes began to sync with the AppleTV, moving content from my library to the unit. As the content flowed into the unit, it started showing up as I navigated around the menus. Video content first, then music. Photo syncing was disabled by default, but after checking the box on the Photos tab, iTunes began to sync pictures down to the AppleTV.
Some things I noticed while playing around for a couple of hours:
After playing with the unit for a couple of hours, I’m very tempted to get one to stay. However, there are a few nagging details and deficiencies that I’ve found, confirming my suspicion that caused me to cancel my order before they shipped.
Overall, the AppleTV is a very nice unit and very close to the right price point. I think it would probably sell like gangbusters in its present form at $199, but the $299 could easily be justified by the masses if a few of the above criticisms were addressed. While I’m probably going to go ahead with plan B, putting a Mac Mini in instead, I’ll be very interested to see what Apple TV version 2.0 looks like.
And I bet we see it before Christmas.
Apple just released the new 8-Core Mac Pro, with dual Quad Core “Clovertown” Xeon processors. The remaining specs, while still impressive, don’t appear to have been upgraded. Still no Blu-Ray or HD-DVD drive announced, but you know that’s why they have the second optical bay in this iteration of the case design. The price adds a $699 premium over the dual dual-core 3.0 GHZ version.
And I may have missed it from earlier, but it looks now like the price on the 30″ Cinema Display has dropped $200 to $1,799.
Rumor has it they were waiting until Adobe CS3 finally shipped to go ahead and release this box, but I think it portends a little of what will be shown in just under two weeks at NAB. I’m expecting to see Final Cut Pro Studio 6, with upgrades across the board and some new apps thrown in the box, as well as an upgrade to Xsan and a preview of Leopard. The grapevine has Leopard shipping in June (perhaps to be officially announced at the WWDC).
Why is it when I go to copy a 270+GB folder of stuff from one drive to another and the finder runs across a bad sector half way thru it just throws up it’s hands and quits? Why can’t there be an option that says “if unable to copy a file, note it and move on”?
I mean really, how hard would it be to just go ahead and copy all that you can, then throw up a dialog that says “These particular files didn’t get copied, and here’s why…”?
Oh, that’s right, it’s just easier to stop on errors rather than gracefully recover.
Ugh. Oh well, one for the wish list in Leopard.
And yes, Windows behaves this way too.
Today’s Apple Goodness:
Oh, and the “One More Thing”: coming Q1 2007: iTV (set top box, wireless streaming)
Many other little details announced. Very cool.
The wonderful time-waster known as Google Earth is now available for the Mac! Go get it, but don’t open it until you’ve got a little free time with nothing due!
OK, here we go again. Apple’s been busy, as usual. Still trying to digest. Will comment later.
(I stole that headline from a buddy of mine, but it seems to fit)
So, for the past week, I’ve been configuring a rack of coolness for a customer. Namely, an 11TB SAN built on Apple’s Xsan/Xserve/Xserve RAID products. In a word, sweeeeeet.
What you see to the left is (from the bottom up)
|
It was touch-and-go at the beginning of the week… I had the servers all gen’ed up with OS X Tiger Server when I realized that the currently released version of Xsan (1.0.1) wasn’t certified for Tiger. Not only wasn’t it certified, it wouldn’t allow you to even attempt an install on Tiger.
This being WWDC week, however, brought the release of 1.1, which in addition to being Tiger certified, supports volumes in excess of 2 TB.
The RAIDs are split into three logical volumes; a metadata volume (two drives, RAID 1), a DATA volume for shared home directories and such (5 drives, RAID 5), and a huge VIDEO volume (3×7 drives, RAID 5 striped).
Talk about performance. When you get everything spun up, it really hums. As a test, I created a 5GB file and moved it around in various ways. Basically, I can move it off the desktop of a client machine onto the SAN in about 85 seconds. Five GIGA (that’s Billion with a G) BYTES in under a minute and a half.
Sure is fun to watch all the little blue lights flicker when the bits are flying.
We de-rack and deliver tomorrow. Hopefully the integration will go smoothly.
wow. Didn’t believe it. Didn’t want to believe it. Still think there’s something more to the story that we’re not getting yet. This’ll be interesting.
powered by wordpress 3.0.4
12 queries. 0.318 seconds