Dead Ink Vinyl » macbookpro

Hands-on with the new Apple laptops

dlkinney — Sun, 19 Oct 2008 16:34:07 +0000

I got to spend a few minutes with the new MacBook and MacBook Pro in the Oak Brook Apple Store on Saturday. Visually, the new laptops are stunning. When they are closed, they look sleek, yet rugged. When they are open, the screen is brilliant — crisp, with fantastic colors. The glass does have glare, but I was unable to gauge how bad it would be in practice. (In truth, I do very little work on my laptop outside of controlled — or controllable — environments, so the whole glare issue isn’t high on my list of concerns.)

My wife doesn’t like the black keyboard, but I pointed out that it matches the black border around the screen. I only performed a little typing on the keyboard, so I can’t report how well it would feel to use for extended coding or writing sessions.

The “trackpad-as-button” was far more intuitive to me than I expected. My reflex is still to press at the bottom of the trackpad where the button is located on my MBP. All of my existing mousing and clicking gestures worked flawlessly, so the migration would seem to be painless for existing Apple laptop users. I then played with clicking and click-dragging the new way, by just pressing my finger down in-place to click. This worked exactly as advertised and feels pretty natural. I believe that I would find it very intuitive if I were using an Apple laptop for the first time and did not have preexisting muscle memory for these operations. The new gestures enabled by the design feel far more ergonomic and comfortable, so I believe I will invest the time to retrain myself when I eventually get one of these laptops.

Posted in Review, Uncategorized Tagged: apple, handson, laptop, macbook, macbookpro, Review, trackpad

Time to Learn Objective-C

dlkinney — Mon, 10 Mar 2008 15:25:47 +0000

Up to this point, I have avoided learning Objective-C and Cocoa. My professional software development is almost entirely Web-based or client-server applications and I haven’t had a lot of itches to scratch when using my Mac. The excellent independent developer community that surrounds the Mac has delivered all of the software I’ve desired and done it at very reasonable prices. Then there is the Objective-C language itself. Explicit memory management and dealing with some of C’s quirks (for example, processor directives) really feels like a step backward from Java and .NET. So there’s never been a lot of incentive for me to embrace Objective-C and Cocoa.

Then the iPhone SDK was released. As it happens, I have several itches to scratch on the iPhone. And the iPhone is a fun platform, too—I mean, there’s got to be some way for stodgy business applications to make use of the iPhone’s 3D motion sensors, right?

So this weekend I joined the iPhone developer program, downloaded the iPhone SDK, dusted off my copy of Cocoa Programming for Mac OSX, and got down to business. Since I have a strong object-oriented programming background due to my time with Java and I’m comfortable with weakly typed languages due to my time with PERL and Ruby (I’m thinking of mix-ins), the single chapter on Objective-C was sufficient for me to grasp the major components of the language. I assume when I’m done with the book I’ll be comfortable with Obj-C’s idioms and familiar with Cocoa. However, my advice to people interested in learning Obj-C or Cocoa is to wait for the 3rd Edition of the Hillegass book.

First, there are several places where the page layout is off. For example, between pages 69-70 several paragraphs are lost. But don’t worry, between pages 71-72 you get a whole paragraph repeated! It’s not a huge deal, but it is annoying.

More importantly, the 2nd Edition is written for Xcode 2. Unfortunately, Xcode 3 is very different from Xcode 2, so many of Hillegass’ screenshots and instructions for using Interface Builder aren’t even close to accurate. The “Hello World” application from the first chapter can’t be constructed. I was more than happy to try slogging my way through anyway, attempting to convert the book’s instructions into Xcode 3 operations, but it was all too new to me. Fortunately, Matt Long has an excellent tutorial filled in the gaps sufficiently for me to progress further. However Matt Long’s solution involved writing the necessary Obj-C class by hand, so I had to read Hillegass’ introduction to Obj-C before things clicked.

I’m now a quarter of the way through the book and I’m really enjoying Obj-C and Cocoa. Writing applications for the iPhone is going to be a lot of fun.

My iPhone is My Primary Computer

dlkinney — Sun, 09 Mar 2008 20:16:09 +0000

Somewhere in the last six months, the iPhone overtook the MacBook Pro as my primary computer. I don’t know when it happened—it was an imperceptible, gradual shift in the way I organized my life. I intended my iPhone to be used as a lifeline for those times I didn’t have WiFi for my laptop. I knew this included all of the time I spent at work, but I’d gotten along fine for the prior three years being disconnected from my personal communications during the business day. I thought would be using the iPhone’s email capabilities for “emergency” communications: last-minute Toastmasters meeting coordination and the like¹.

Now, I use the iPhone every day and it handles my the majority of personal computing needs. It’s convenient and (generally) a joy to use. I don’t appreciate being sent to my secondary computer for tasks I should be able to accomplish on my primary device. I don’t like opening my MacBookPro to surf the Web. Or to read email, record appointments, update contact information, or even to tweet. In fact, I only look forward to using my MBP for coding, blogging, writing documents, and image manipulation. For my everyday online activities, I far prefer using my iPhone. When I have to use my MBP for an “iPhone activity”, I get irritated.

The irritation has been increasing over the last couple of months. Mostly, my irritation is incited by Web sites that don’t lend themselves to ease of use on the iPhone (for example, my beloved Highrise)—or worse, completely disrespect the fact that I’m on a low-bandwidth EDGE connection (for example, Grub Hub, which I saw advertised on the CTA but had to dismiss because the home page took more than three minutes to load).

With the release of the SDK, the iPhone is graduating to become a full computing platform. It will move beyond email and Web sites². I anticipate that the coming year will see the release of all the applications I need to avoid cracking open my MBP for any of the mundane stuff. Finally, I’ll get to use my iPhone for instant messaging, enjoyable Twittering, Highrise, and WordPress.com administration.

Even if I have to build those applications myself.

¹ Of course, looking back on it, I note that my first mobile phone was purchased “for emergencies”, but very quickly became my primary phone service. Perhaps this is a general pattern for adoption of new technologies.

² To be honest, Web applications have really carried the iPhone farther than I expected. There are some very talented and dedicated people out there who pushed the Web on MobileSafari far beyond what I imagined possible.

More Info on MacBook Java Performance

dlkinney — Fri, 31 Mar 2006 04:56:00 +0000

The OpenLaszlo Project Blog gets some benchmarks of Java performance on the new MacBook, relative to the G5.

So the second thing that happened is that we got a shiny new MacBook. Today I compiled LaszloMail on a co-worker’s desktop G5, and the shiny Intel thing. Ready?

G5 (dual 2ghz, 1 gig RAM), OpenLaszlo 3.2: 32 seconds

MacBook Pro (dual core 2ghz, 2 gig RAM), OpenLaszlo 3.2: 17 seconds

Hot damn!

You said it.

Some Java on Intel Mac Benchmarks

dlkinney — Sun, 05 Mar 2006 02:15:00 +0000

In a previous post I wondered about the Java performance on the new Intel Macs. I now have a benchmark.

Okay, the term “benchmark” might be too strong. I ran one of my favorite applets on the 15″ MacBook Pro while at an Apple Store today. I took screen shots of the results to compare to the performance of my own PowerBook. The applet is a 3D visualization of a Kohonen Self-Organizing Map. The Kohonen Map is a type of neural network used to automatically group similar inputs and provide visiualization of large quantities of data. Another interesting application of the Kohonen Map is to solve very large TSP-type problems.
Anyway, this applet is interesting because it has simple 3D graphics, lots of floating point and integer math, and possibly a good amount of object allocation and garbage collection. I don’t know if the applet is multi-threaded, though, but by the results I would guess that it is not. Thus, this is a highly imperfect comparison between the PPC and Intel Macs.

System specs:
PPC: 17″ 1.33GHz PowerBook with 1.0GB RAM
Intel: 15″ 2.0GHz MacBook Pro with 1.5GB RAM

Raw Results:
PPC:

Intel:

Numbers:
PPC: 1107 learning cycles in 138.697 seconds (7.981 learning cycles / second)
Intel: 1100 learning cycles in 62.514 seconds (17.62 learning cycles / second)

X-Factor:
The MacBook Pro is 2.2x faster than my PowerBook on Java performance. Assuming that the applet is single-threaded, the MacBook’s JVM 1.47x more efficient per CPU clock cycle.

I’d like to also note that the applet’s 3D animation was much smoother on the MacBook than it was on my PowerBook.