What’s really sad about this whole deal is the disparity between the usefulness and elegance of MacRabbit’s CSSEdit and Espresso. CSSEdit is wonderful, Espresso is sorely lacking, and a huge disappointment.
I love CSSEdit too, it’s a critical part of my toolset and workflow. The utility and innovativeness of that app is what lead me to give Espresso a try. I think Espresso still has promise. I never used CSSEdit before 2.x ... but I can imagine it must not have been as refined and as solid as it is now when it was first released. So a comparison between CSSEdit 2.6 and Espresso 1.0.5 may be like comparing an adult to an adolescent.
Espresso’s minimalist interface is appealing to me. The hierarchical Navigator makes it quick for me to find and highlight blocks of code. Creating your own syntax highlighting theme is flexible and simple. The extensibility of the languages through Sugars allows for code completion for EE tags. The Publish mechanism makes it very clear what files will be changed between your local machine and the server, and you can set the preferences on a per file / per directory basis so Espresso remembers them. The tool just needs some refinement and polish.
So for me ... the main concern is more “where have the MacRabbit developers gone, when are the refinements coming, what is the roadmap for the future of the app and why hasn’t there been a word from them since MacHeist”. Which leads me to think (being the skeptic I am) that they got a nice chunk of change from MacHeist and took an extended vacation. Would they have done the same if MacHeist was not so successful?
Hopefully, we’ll hear from them soon (http://twitter.com/CaptainNeutrino August 5 tweet).