Note: Several commenters have provided valuable feedback that I am responding to with updates to this post and in the comments. Make sure to read both!


On yesterday's WWDC keynote, Steve Jobs introduced "FaceTime" and explained its base technologies with the following words:

"Now it's based on a handful of standards... but this is going to be an open industry standard."

I wish Steve Jobs would cease calling H.264 and similar standards "open". Technologies that cost millions of dollars to use are, by definition, not open. He can hope it'll become an "industry standard" (as in, used by companies apart from Apple), fair enough. But he can't say it is going to be "open". That's like a college kid calling the grocery store "free" just because daddy gave them an unlimited credit card. And it's doing a huge disservice to the Open Sourcestandards community by misusing the term in the worst possible way.

Quote and photograph courtesy of Engadget. Thanks!


Update, 4/9/2010: For a while, I removed the above text in order not to express unwarranted criticism towards the speaker. After several rounds of user feedback, however, I decided to keep the original text and update/annotate this post as necessary.

Update on the definition of openness:

As Sandy pointed out in the comments, there are many definition of what standards are considered "open" and depending on which of these you follow, varying licensing fees, as long as you don't exclude anyone with enough money to buy them, are still valid for calling a standard "open". I disagree with that view, but it is a possible interpretation.

Commenter Dave mentions that Steve Jobs usually makes sure to call actual open standards "open" and calls H.264 and similar technologies "industry standards" instead. He is therefore likely to know the difference between the two, even though calling an entire stack "open" in spite of some of its components not matching that definition is a strange, or even misleading, point of view.

Finally, Jo argues that the mere fact that other vendors can build devices to connect to the FaceTime stack instead of it being limited to Apple products only makes it "open". In other words, this use of "open" would be a synonym of "standards compliant". I believe that is still a very limited view on openness, but at least it is more open than the alternative: a locked-down proprietary solution.

Peter also reminds us of the technical limitations: Since all mobile devices need hardware support for video encoding and decoding, Apple had to settle for H.264 a long time ago, and even if they wanted, they could not simply switch over to a different codec. Most people (me included) also seem to agree that H.264 is -- from a purely technical standpoint -- a good choice for the FaceTime stack.

Read more…

Over at AppleInsider, they have a bunch of photos comparing the new 15-inch Macbook Pro with the now "old" design:

My thoughts: The new MacBook Pros are a really worth thinking about. From their overall look, they seem to be better designed, and a few annoyances have been taken care of, such as the old MBP's plastic rim, or the hard drive (failure part number one in computers, seriously) that was hidden way on the inside of the box.

Along with that, since I bought my first-generation one, the processor speed (mine still has an Intel Core Duo CPU), and now also graphics power have increased significantly. All the new "bling" in Mac OS X Leopard and many new and fancy applications demand a lot from a laptop, which mine--in spite of plenty of RAM--sometimes can't fulfill.

Bottom line: I am considering retiring my laptop "Chronos" some time next year as my primary, every-day tool, in favor of one of its younger siblings, with much more "bang" to tackle the work to come.

I also looked at the smaller MacBooks, and while I like that they moved closer to the MBP (being aluminum and all), the missing FireWire, ExpressCard, and the shared-memory graphics made me forget about that pretty fast.

Read more…

As we established before, X11 on OSX 10.5 Leopard is, at least kind-of, broken.

Gladly, there are numerous community efforts to bring our tragic hero back on stage. For example, like in OSX 10.4 Tiger, it is possible to deactivate the XTerm window starting up every time you start X11. It has just become a little more complicated.

First, this is what has changed with launching X11 on Leopard (as described on boredzo.org):

In Tiger, when you launch X11, it runs .xinitrc, and .xinitrc runs xterm (unless you comment that line out).

In Leopard, X11.app is just a launcher. All it does is run /usr/bin/login -pf $USER /usr/X11/bin/xterm. In other words, its only purpose is to run xterm (semi-)directly, by itself--it's not the actual X11 server anymore. When xterm starts, launchd sees it, notices that xterm requires X11, and launches the real X11 server (/usr/X11/X11.app) automatically.

In other words, there's no commenting out a line in .xinitrc anymore in Leopard. Instead, we need to change the launcher itself (as described in the very useful X11 on Leopard FAQ on macosxhints):

defaults write org.x.X11_launcher app_to_run /usr/X11/bin/xlsclients

Instead of xlsclients, we can alternatively run xprop (thanks, JP!). Both applications have the good habit not to do much (i.e. not to waste a lot of cycles/energy/water/CO2/whatever) and also not to open an annoying window like xterm does.

Hope this helps :)

Read more…

Gimp LogoOn our neverending bug journey though Leopard land, here we go with the next episode: X11.app in connection with the Gimp.

Apparently, Apple did not find time to test one of the (if I had to guestimate) most used X11 applications on the Mac with their newest version of X11. Therefore, X11 on Leopard crashes frequently with the latest Mac version of the Gimp image editing software.

Also, when you pick, say, the brush tool and move it over an image, the tool pointer sluggishly follows the mouse pointer around until, about 2 seconds later, they meet up again. This looks funny, but makes actually using the Gimp kind of impossible.

Fortunately, the bugs in the shipped version of Leopard can be resolved by installing upgraded versions of libX11 and Xquartz as described on the X.org Wiki. This worked flawlessly for me, but make sure to make a backup of the libraries before you replace them, in case something goes wrong.

By the way: Does anyone know how to remove the XTerm window that always pops up when X11.app starts?

(Thanks for the link, Jean Pierre!)

Update: The RC3 version of Gimp from gimp-app.sf.net seems to lead to problems, even after fixing X11 as described above. However, until the gimp-app guys release the stable version (currently: 2.4.1), there is a community build available from Nasendackel (German). Good job!

Read more…