Archive of June 2008

June 24

Nemo, Wall-E writer/director: Listen to your gut, not the audience

Andrew Stanton on not anticipating what the audience will or won’t like:

That’s the part of the film audience to trust — the audience in ourselves. We don’t need to guess what other people want. I don’t go to see another filmmaker’s movie hoping he’s guessed what I want. I go to see it because I like his sensibility and I want to see what he wants to do next, or she wants to do next.
02:32 PM
June 19

Wonderfully irritated with the OmniFocus UI

Matt Neuberg just wrote a somewhat positive review of OmniFocus, but he lambasts the user interface, even recording some screencasts to demonstrate the interface’s shortcomings. I love just how audibly peeved Neuberg is. And rightly so! Good for him.

Via Gruber.

05:19 PM
June 17

To avoid Flash lock-in, Apple looks at SproutCore

Matt Asay writes about SproutCore, the Javascript framework behind Apple’s “Cocoa for Web Apps“ concept:

It will be interesting to see if this gamble on a relatively unknown open-source JavaScript framework will pay off—or whether it would have been easier to just buy into Flash. Apple has the developer clout to make it pay off, but for most developers, Flash or Silverlight are likely going to be better options.

By “Flash or Silverlight” Asay probably means “AIR or Silverslight”, but why are these going to be better options for developers? I’m no Cocoa developer myself, but from what I can tell, devs are very happy to work with Cocoa. Apple could release a “Cocoa for the Web” integrated development environment that would beat Adobe’s and Microsoft’s IDEs for AIR and Silverlight.

Once the browser-specific hoo-ha and Javascripting jumping jacks are handled completely by a framework like SproutCore, and once there’s a beautiful IDE to work in, and when there’s no proprietary plug-in needed because all the underlying technologies are open-source, I’m not so sure AIR and Silverlight will be the tools of choice.

11:36 AM
June 16

Apple's path to domination: first web apps, then the world

In February, I wrote about Apple’s updates to Safari:

Apple is positioning Safari as the premier platform for web applications. They’ve got something up their sleeve, with last year’s port of Safari to Windows and with MobileSafari on the iPhone — should be fun to find out what it is.

Daniel Eran of RoughlyDrafted.com may have the answer:

Apple is refining Cocoa for deployment within the web browser to enable developers to build those so called “Rich Internet Applications” that Adobe wants users to build in Flash/Flex/AIR, Microsoft in Silverlight, Sun in Java, and so on.

I’m not sure how or why Eran is reporting all of this as fact, but this is a really intriguing idea — that Apple may be positioning Cocoa, its primary OS X application coding environment, as a platform for web app development. This could explain why Apple ported Safari to Windows, why Apple is pushing for faster Javascript performance in WebKit (the open-source browser engine behind Safari), and why Safari includes built-in database storage.

What this means for web apps is that programming web apps could, by and large, look exactly like programming for OS X. From my limited knowledge, programmers who code in Objective-C/Cocoa love it; I doubt the same is true for AIR, Silverlight (or .NET for that matter), or Java. Plus, the platform for distribution, according to Eran, would be completely open. This gets at one of the things I find so wrong about Flash: web development shouldn’t have to rely on proprietary app development tools. (My guess is Apple feels the same way, though surely their opinion involves more than my aesthetic dislike.)

But how does Apple benefit from an open web framework? A RoughlyDrafted reader offers some interesting, though of course highly speculative, thoughts: by creating an OS-neutral platform for not only their own apps (like the MobileMe apps), but for web apps at large — and one that web developers will actually flock to — the importance of the OS as a “platform” becomes meaningless, because the platform is the web. However, you still need an OS to get to the web, so the OS’s qualities as a program (security, performance, UI, etc.) become paramount. When the question of install-base and entrenchment no longer matter, the OS battle lines can be drawn up over the operating systems as apps themselves. OS X will, of course, win that battle.

(I think this is actually a large part of why Macs are already increasing in market share so dramatically: 95% of what people use their computers for is (web-based) email and browsing the web. You don’t need Windows for that.)

12:36 AM