I’m an avid Coda user and it’s not for lack of exploring. So you can calibrate my opinions, I’ve given the following text editors at least a ride around the block.
Dreamweaver
TextMate
BBedit
komodo Edit (pro)
Espresso
Aptana Studio3
CSSedit
So with that being said…
love
1) One Window Development
I am a complete type A personality when it comes to the organization of my Mac. Among the things I hate the most are loose files (anywhere), a cluttered desktop and possibly the worst of them all, layers and layers of application windows stacked on top of each other. I like to at least see a sliver of my desktop somewhere. It’s so easy to get going and leave a few photoshop documents up, your FTP client, a browser or dozen open and of course there is the distracting things like twitter apps and iTunes etc etc… At least Coda combines a very capable FTP client, terminal, preview and element inspector. I dont’ care for Dreamweaver and the many WYSIWYG panels that take up valuable screen space. Coda is clean and simple. Some sort of split screen feature is an absolute must for me now.
2) Sites
Not only is the sites tab all pretty looking, it saves all your FTP/local information and keeps an updated thumbnail of your site. If you have to shut down coda or switch projects, when you return it’s as if you never left.
3) Themes
You can change your editor colors very easily. This not only easily distinguish what exactly is going on in your varying syntax but it helps keep things festive too. Take a look at Justin Hilimen’s themes for great examples. I love customization. Being able to customize the color of each syntax (with the added options to bold or italic) is very helpful when scrolling through lines and lines of code.
4)Split Panes
Can’t live without this feature now. Most common set up for me during development is : (from left to right) Main monitor = File browser>CSS>whatever file I might be working on. Second monitor = A Coda preview window and 4-5 other browsers neatly stacked up 
. I find this setup creates a situation where most everything is right in font of me and very little window swapping is needed unless I need firebug, photoshop/illustrator or another browser.
5)FTP
Along the lines of one window development but more specifically, the publish feature (or reverse publish). Being able to work locally on a specific file and then shoot that to the server when I’m done is awesome. And of course, Coda remembers the FTP credentials so I’m not bothered by a username and password prompt.
Hate
1)Code folding?
Um, no. No real need for elaboration here. It doesn’t exist and it really needs to. I can live with other nuances of Coda, except for this one.
2) Code Hinting & Completion
It exists, but it’s marginal at best. Works pretty well for all things HTML or CSS I find, but I find it’s quite lacking when it comes to all things javascript and PHP. I’m sure the same can likely be said for other languages. I just don’t work with them enough to know.
3)One window development
Yup, I also hate it. For one very specific reason – it doesn’t really play nice with a double monitor set up. This is one area that all things adobe really excel. The whole panel approach is perfect. Drag all your panels over to one monitor, expand them, tile them and everything is at your fingertips leaving the other monitor wide open for code, graphics or whatever it is you are working on.
With Coda, I use two separate windows. Problem is, the second window isn’t actually part of my site as far as coda is concerned so I can’t really click on the file on the main monitor and have it open on the second. Likewise, I can’t drag and drop it into a pane to open it either. Basically, files need to be open from the file browser within the window you’d like it opened in. Yes, I could have two file browsers open, but that’s redundant and not exactly the workflow I’d like to be working towards. I suppose you could stretch the window across both monitors assuming they are of identical resolution (mine are not), but I’d imagine that would just be weird.
4)CSS color picker
Ever write CSS in Dreamweaver? Hex value colors in particular? As soon as you type “background: #” a little WYSIWYG widget pops up which allows you to select a color. After years and years of working in graphic related fields, I’ve stored a great deal of colors in my brain in HEX format, but sometimes I need something a little more specific or obscure. I’m aware of Coda’s WYSIWYG CSS editor, but I find it faster to just hop ever to photoshop then to switch to the CODA CSS WYSIWYG editor, sort through all the selectors, find the one I need and change it.
5)Updates
Don’t expect a whole slew of them. Not a whole lot of transparency when it comes to future updates, dates or anything like that. I subscribe the to the unoffical coda email list and you can almost set your watch to the new threads that are somehow related to “When is Coda 2 going to be available?” In a somewhat recent related thread, a Panic employee jumped in and said the following:
(It’s been a while since I’ve popped in here to apologize for how slow this stuff goes. So, here I am. )
I liked Coda a lot, I would sooner not use a Java application, but
really 3 year’s without an update !?!
Well, technically, our last update was on November 5th, 2010. But I know your point.
We’re working on a major update go, these take an incredible amount of work and effort for us. We’re not just going to slap features on top of Coda 1. That’s something a lot of major software developers would do. We see Coda 2 is an opportunity to step back, look at the program as a whole, and make foundational improvements to the app. Put simply, this is a huge project.
Also, keep in mind that the last few years we were working on Transmit 4. This is the challenge of a small company — there’s only so much (in our case, ‘one’) we can do at one time. Sorry about that.
For the record, it took us nearly 5 years to go from Transmit 3 to Transmit 4. And ironically, while we were working on Coda, everyone was angrily wondering where Transmit 4 was. (“Why are you wasting your time on Coda!?!”) So it goes.
I also resent the absolute lack of communication from Panic – it is an
insult to once loyal customers.
What can we say? We can’t post predicted schedules because we’re guaranteed to be wrong and people will go absolutely crazy. We can’t talk about features because we’re in active development and competitive edge is important. Well, that doesn’t leave a lot to say.
As I said in our “State of the Union” post, once we hit beta, we’ll let everyone know. Until then, there’s virtually nothing we can talk about. My legitimately sincere apologies.
Their news feed suggests that rather
than writing software they more interested in cooking dinners than
writing software.
No. We post about dinners because we can actually talk about them. We can’t so much about still-under-development software. As funny as it is to imagine that we’re somehow choosing to eat instead of code (maybe we should eat while we code?), you know, if we didn’t eat we’d die. 
I know waiting sucks, but it doesn’t suck half as much as being on this side of the coin…
Trust me: I wish Coda 2 was out approximately 500 times more than you do.
Best,
Cabel
So, take that s you will. They are clearly a small company and I can’t say I’m all that surprised with the way things are although a few more tidbits like the above e-mail would really go a long way in my opinion. At least let us know that you haven’t jumped ship on a product line like so many other companies have in this economical climate and left us using a terminal piece of software, or worse yet, training employees to use it.
In the end, Coda is still my favorite and my daily driver when it comes to a text editor. There was a point where I became a little impatient with it’s short comings and started shopping around. I can say for sure, Java based editors are way to clunky and slow. I don’t know why, but it just seems to work out that way. If anything, it’ll be Espresso that will tear me away from Coda. That is, if Panic takes an unreasonable amount of time to release Coda 2.
4 comments so far
March 5, 2012Interesting post, but when was it written?
Articles like this are a lot more relevant iy you know *when# they were written.
Thanks
The one and only Wim Heitinga
March 5, 2012Thanks for checking in. The date is on the blog page and at the top of the page.
March 8, 2012what bugs me the most are two things you mention, and two more that you don’t (but one might still be an extension of one of them).
1) code folding! code folding! CODE FOLDING! the IDE arguments all over the google groups are for jerks who feel they have to prove that they’re superior to the rest of us who want efficient low file counts for normal web dev, not hardcore coding.
2) css color picker, and other hinting… I still usually write all my own colors since I shorthand them when possible, but I see the need for it for the casual users and newbies.
3) integrated code hinting… this is more than the css colors, it’s the smart multi-file (or I should say “site”) awareness that dreamweaver exhibits: if I’m working in a site, the items in the related css files should be available in the html as I write it. ids and classes autocomplete within a DW site so well, but do nothing in coda. this also goes for more advanced features like autocomplete in css for background urls, or include files. it’s lacking in DW too, but would be great to have in both.
I doubt I’ll ever be able to abandon DW, simply because coda isn’t smart enough to be fully aware of all “sites” locally. DW gets the download a file, work on it, and upload it process just right. I hate that I have to remember to download backups after a couple hours of working on files just to make sure I don’t lose them. this doesn’t have to be by default, as I know plenty of people work in a staging server environment with a group of people co-writing. but to have the ability to do so would be ideal. we have the ability to work locally or remotely, why not both in an integrated approach.
by extension of this, DW’s ability to manage the “site cache” is a godsend when not creating a site from scratch. I’m currently working on a site with 100+ html pages that are being converted manually to php and stripped of extra markup in favor of sharing includes and other stuff. also, the images directory holds 200+ subdir that are horribly-named including spaces and bad characters that I want to remove. in DW, I can change those files or folder names and let it seek out every instance of that used in the site and auto-fix it, and then in the end I just re-upload all files and folders. to do this in coda would be a nightmare. manually changing every filename and folder name, and then having to search every file manually to replace and update each instance. no thanks.
I really like coda so far in the six months+ I’ve been using it, but if it wasn’t for all the other bloat in DW, I never would have considered switching in the first place.
March 9, 2012Totally right Jeremy. I’m not too man enough to use a IDE.
There is no doubt that DW is a very powerful editor. I think it’s the cost that rubbs a lot of people the wrong way. Yes, it’s somewhat bloated, but it’s still fast and if you really use it for as an editor and not a WYSIWYG then certainly works.
Coda roped me in with sleek design, speed and if you have ben a long time mac user like me, I’m not sure there is a more intuitive editor out there. That, and the built in FTP/sites features are second to none. After that, things get a little more complicated. No doubt.
I’ve somewhat recently switched to Sublime Text 2. It’s not as pretty, is much harder to wrap your head around but is FAR more powerful thanks to huge development community around it. Not to mention it’s still in it’s beta stage. There are some clear advantages to a multi platform editor.
I was eagerly awaiting Coda 2. At this point, I’m afraid it might be too little, too late. Stay tuned