A new trackpad firmware update, version 1.0, is available for the new MacBook and MacBook Pro models (listed as late-2008 models).
This firmware update addresses an issue where trackpad clicks may not be recognized on MacBook (Late 2008) and MacBook Pro (Late 2008) systems.
A Google search for Apple Dual-Link DVI yields a ton of product pages and blog posts about the greatness of Apple’s use of DVI. You’ll get quite a few of Apple’s own product pages, as would be expected. But only a few blogs are calling Apple out.
Apple recently released a new MacBook Pro. It has the most advanced laptop graphics equipment on the market, with dual NVIDIA 9400M and 9600GT chipsets. Apple has also employed a new port type, DisplayPort, that is not the same as Mini-DVI or Micro-DVI. This is a port that is easier to plug in than DVI and supports HDCP (high-bandwidth digital content protection).
People with needs for the best processing horsepower on the go are going to pick up this laptop. These professionals, myself included, are going to be disappointed. If you’re in to a high-end laptop like this you’re probably also pushing 30″ monitors. If not, you should be. But you can’t. The DisplayPort to Dual-Link DVI adapter doesn’t ship for 4-5 weeks (and that’s what they said on October 15th).
The image above is the dual-link DVI adapter from Apple. It’s a DisplayPort plus USB plug to a DVI female. Why does a dual-link DVI adapter require the addition of a USB plug? Giving up that extra USB port hurts. Paying Apple $99 to move us to a new port type is insulting.
So what’s with the delay? It doesn’t take 4-6 weeks to manufacture cables with DisplayPort, USB, and DVI plugs attached (the site has displayed 4-5 weeks for 4 weeks already). Either development of, or problems in, the circuitry is derailing Apple’s rollout. Or perhaps software driver updates will be required before the DisplayPort + USB adapters can be driven. If the latter, we would expect the adapters to ship at the same time as an OS update drops.
Apple, make this easy. Make it just work…
For more on DisplayPort see DisplayPort: what you need to know (Peter Cohen)
And for a little ridiculousness:
UPDATE: Another theory is that the chip for the adapter requires additional juice. The USB connector would simply be a power chord.
On June 28th, 2007 I waited in line for the iPhone (and spent 3 days talking to AT&T to get it activated). The experience was a good one… The stench of rotten trash from a nearby McDonalds dumpster and seeing a full-grown man get beaten by his girlfriend and her purse for spending the $500 are favorite memories.
Normally I’d be all over the line parties (seriously)… This year I slept in and am happy to wait for it to arrive in the mail. Maybe next year.
vs 
.
That’s it! Twice in a week I’ve been left with a dead iPhone from snapping pics and pushing them live at an event or outing. Don’t get me wrong; I love the iPhone for most everything, but the lack of a swappable battery is adding some hate to the relationship (lack of video has also been a bone of contention).
The Nokia N82 is looking like a sweet option. Everything but a useable keyboard…
I was very pleased by a question in today’s press Q&A at Apple’s iPhone SDK release announcement. I posted the other day about the iPhone SDK being in development since before WWDC ’07. The question pertained directly to my thoughts, “Why did you change your mind about the iPhone open SDK? How long will apps be vetted before being published?” (actually, two questions).
Steve answered, “We change our minds a lot. The web apps have worked well, but developers wanted to do more. And we heard that. Creating an SDK is a lot of work, you want to make it something you can live with for 20 years, and yet update it without breaking apps. This is an elegant and clean system.”
I’m certain Apple had the SDK in development since before WWDC ’07. As Steve said, it takes a long time to develop an SDK. They just weren’t ready to announce it yet last year and covered by offering web apps. Their marketing machine and product release practices entice us to want more. We hated Apple last summer for it!
The remainder of the question was handled by Phil, “Second question. Electronic submission will be very fast, and this is a whole new process.”
A lot of people are screaming bloody murder about Apple controlling this process. While I don’t really like the idea of only getting Apps installed via Apple’s system, it could be a lot worse. Apple will be CHiPs, not the DMV. There will undoubtably be apps which make it possible to download and install while being untethered anyway.
The impression I got during the sign-up process to develop for the iPhone and download the SDK was impressive. Not because of the smoothness of the process (I hit terrible snags due to the server congestion), but because it’s obvious they’re going to allow developers to easily publish apps. What I got out of it is they’re making it better and easier to write software for the iPhone than for Windows Mobile or other handhelds. Apps will be as easy to publish as an album of music… Same model.
Dave Winer has been leaning towards the negative side of Apple’s plans, but he likes the idea of an untethered podcatcher. I’d love to talk to him about that… It’s something I expect iofy to work on.