E-Scribe : a programmer’s blog

About Me

PBX I'm Paul Bissex. I build web applications using open source software, especially Django. Started my career doing graphic design for newspapers and magazines in the '90s. Then wrote tech commentary and reviews for Wired, Salon, Chicago Tribune, and others you never heard of. Then I built operations software at a photography school. Then I helped big media serve 40 million pages a day. Then I worked on a translation services API doing millions of dollars of business. Now I'm building the core platform of a global startup accelerator. Feel free to email me.


I co-wrote "Python Web Development with Django". It was the first book to cover the long-awaited Django 1.0. Published by Addison-Wesley and still in print!


Built using Django, served with gunicorn and nginx. The database is SQLite. Hosted on a FreeBSD VPS at Johncompanies.com. Comment-spam protection by Akismet.


Pile o'Tags

Stuff I Use

Bitbucket, Debian Linux, Django, Emacs, FreeBSD, Git, jQuery, LaunchBar, macOS, Markdown, Mercurial, Python, S3, SQLite, Sublime Text, xmonad

Spam Report

At least 237138 pieces of comment spam killed since 2008, mostly via Akismet.

PyObjC in, Cocoa-Java out

The Apple Developer Connection recently posted what looks like a nice introduction to PyObjC. It's even got QuickTime movies showing how to work with Interface Builder. Cool. The enthusiasm on the page is palpable:

PyObjC's maturity is unmatched - it's been around longer than even Apple's Java bridge (it originated on NeXTstep).

Meanwhile, in case you missed it, the Cocoa-Java bindings are deprecated:

Features added to Cocoa in Mac OS X versions later than 10.4 will not be added to the Cocoa-Java programming interface. Therefore, you should develop Cocoa applications using Objective-C to take advantage of existing and upcoming Cocoa features.

This is a watershed moment, I think. Python is a language Apple enthusiastically endorses for building Cocoa apps, while Java is emphatically not. Wow.

Apple's taking a gamble here. I imagine that among other factors they expect to get better, more Mac-like applications via PyObjC than Java. This will rankle the Java folks, of course. And when we see the first official tutorial on the Ruby-ObjC bridge the rioting will start. But Apple's never been particularly averse to pissing off developers -- often to the company's detriment. I hope this works out happily.

Wednesday, August 17th, 2005
+ + +

0 comments pending approval
Comment from Norman , later that day

I wonder if this could presage a step only mildly less dramatic than the Intel switch - moving from Applescript to Python?

Comment from Paul , 1 day later

Interesting suggestion. Seems unlikely, given recent developments like Applescript Studio. Java bindings languished for quite a while before being deprecated. But if they did decide to do it, the proof of concept is there in Appscript...

Comments are closed for this post. But I welcome questions/comments via email or Twitter.