Archive for December 2, 2011

Friday, December 2, 2011

QuickTime History

Tony Smith notes that QuickTime is now 20 years old (via Jonathan Rentzsch):

Looking back, it's easy to dismiss the early QuickTime – with its tiny image size and scratchy, low bit-rate sound – as a gimmick, but the technology was genuinely ground-breaking at the time of its release. Computers had shown video before, but not without some very expensive add-on technology. This was the first time video could be done on an ordinary home machine.

Kindle vs. Nook vs. Kobo Review

Marco Arment:

I’ve been able to generate newspaper-style navigation that works on all non-touch Kindles, but the Kindle Touch and Kindle Fire use new periodical-navigation formats that I haven’t been able to successfully generate yet. I don’t know if Amazon will ever make this possible. And recent changes to Kindle “personal document” storage makes it difficult to delete old Instapaper articles from the Kindle Touch.

He also says that the Kindle Touch is slower at page-turning than the Kindle 4 (and Kindle 2 and 3). I have the Kindle 3 (a.k.a. Kindle Keyboard) and am not at all tempted to upgrade. The Touch lacks page-turning buttons, and the Kindle 4, though a bit smaller, would be significantly more unpleasant for type-to navigation and entering short notes.

Gitbox Is 1 Year Old

Oleg Andreev:

Gitbox is still lacking some interesting things like built-in diff viewer, line-by-line staging, tree view or submodules. Those will come soon. But many more important things were already done: very responsive UI, instant full-history search (even by diff contents), undo for common operations like commit, pull and push (and more to be added in later updates), ubiquitous drag and drop and powerful keyboard shortcuts. Also, a lot of stuff was ignored that would cripple and complicate the UI. Some power features were delayed until the right place for them was found.

Object File Inspection Tools

Mike Ash:

Being able to see all stages of your work can be immensely helpful when debugging a problem. Although you can get a lot done only looking at the source code and the app’s behavior, some problems benefit immensely from being able to inspect the preprocessed source code, the assembly output from the compiler, or the final binary.