This is an excellent update to my text editor of choice for nearly 20 years. Since the public beta, there have been more improvements, such as holding the Option key in “Open File By Name” to open the file in another application, better handling of smart quotes in code files, and an expanded Counterparts menu that makes it easy to view adjacent files.
It’s been five years since our first prototype was saved as dropbox.py, and Guido and the Python community have been crucial in helping us solve interesting challenges for more than 100 million people.
It’s interesting that he’s leaving Google.
The problem with iOS’s solution is that developers can’t expect users to know how to go back to the previous app. As a result, iOS apps almost never send you to other apps. This has a number of negative effects.
A list management software bug exists in the Time Machine volume list— when a volume is unmounted, the exclude list is corrupted, dragging some (possibly mission critical) volumes into the exclude list.
This bug is extant as of early December 2012 in OS X 10.8.2 Mountain Lion (and almost certainly on Lion as well). A bug has been filed at Apple.
In the past few years, quietly, almost invisibly, Apple has transformed its Objective-C language into the best language available. I have been working with Objective-C since the release of the iPhone App Store in 2008. In that time Objective-C has evolved from a clunky, boilerplate-heavy language, into a tight, efficient joy.
There are just the small issues of Web libraries and deployment.
Now Kevin goes on to say what is no doubt the most controversial thing in his entire post: “Xcode is an excellent IDE, with tolerably good git support.”
Update (2012-12-13): Graham Lee:
There are only two problems with this argument: it’s flawed, and the precondition probably won’t be met. I’m sure there is an opportunity for server-side programming with Objective-C, but it won’t be met by Apple.
With the arrival of iTunes 11, classical music fans – and anyone with a large music library – have lamented the removal of certain features and views that help organize large amounts of music. I touched on some of these in my extensive review of iTunes 11 for Macworld, and in my discussion of iTunes 11 on the Macworld podcast. But I would like to summarize here the problems that iTunes 11 has brought specifically to classical music listeners.
I like a lot of the changes in iTunes 11, but there’s no doubt that there are also some big regressions. And despite the “little extra time to get it right,” it doesn’t feel as though it was thoroughly tested. For example, the new “Use custom colors for open albums, movies, etc.” feature produces illegible text for many albums.
