While there’s not really anything revolutionary about the individual components of Coda — remote SFTP browsing, text editor, browser preview, visual CSS editing, SSH terminal, programmer documentation — these functions are rather elegantly stitched together in a way that makes my existing toolset — YummyFTP, BBEdit, Firefox, and CSSEdit — look cumbersome.
The nice thing about Coda for me is that its basic assumptions about work flow mimic closely the way I actually work — editing “live” files from a remote volume via SFTP, previewing in a browser from the remote server, tweaking, repeat. While it’s possible to recreate this flow with things like YummyFTP’s ability to call BBEdit and re-save to the remote volume when the edited file is saved in BBEdit, having a closely-coupled remote volume browser and text editor takes one level of cumbersomeness out of the picture and makes for a much more natural rhythm.
The text editor in Coda, built around the Subetha Engine, isn’t quite as capable as BBEdit — there’s
no function-browser (Wade points out there is one), and the search-and-replace functions are nowhere near as strong (seems like I missed the fact that Coda actually has very capable search-and-replace, with regex and everything!), for example — but it’s a pretty solid text editor nonetheless, and presumably will only get better in future releases.
Indeed one of the pleasant surprises of Coda is that it doesn’t suffer from the “Lotus Symphony” problem, where functionality is compromised for integration.
While there are some interface inconsistencies and other challenges in Coda — the integration of the Terminal application, for example, is visually confusing, and the documentation in Coda’s “Books” is too slow to be practically useful — Coda is remarkably mature for a 1.0 release, and I’ve been using the application for 3 days very productively and with surprisingly few “oh, I can’t do that in Coda” moments.