Some time ago, I switched from MarsEdit to ecto. Mostly, I did this because I liked writing posts with "real" formatting -- that is, using the RTF editing view that ecto offered.

At the time, I was only allowing myself 15 minutes per post, and the HTML I was using in MarsEdit simply got in the way of quickly reading the post for content. Too much translation, the Preview didn't really do it for me... and it didn't look like Brent was going to find much time to work on the program (understandable, given his success with NetNewsWire).

Given that set of issues, I switched. Not all upside (the HTML generated by the RTF translator was rather sub-optimal), but overall it worked for me.

With Daniel Jalkut's recent acquisition of MarsEdit (congratulations, Daniel!), and his flurry of activity improving the core and fixing bugs, I've decided to give it another shot. And to get around the readability problem, I'm giving Markdown a try.

I don't know why I didn't use Markdown before -- probably, I didn't want to learn yet another thing. Maybe I just wasn't aware of it. But I'm glad I've finally found it and taken the time to figure it out. Markdown's pretty easy: natural to read and write once you grasp the basics. JG and Aaron Swartz did a good job with the syntax: it's regular, logical, functional, readable.

And it's supported by Expression Engine, too.

So, three posts later, I'm sticking with it. Hopefully with these few changes I'll be able to find a bit more time to blog!