I am used to coding by hand in DW and my husband uses DW in both design and code mode. We have templates for different posts stored in DW now and edit as needed. Saves us both a ton of time. I have to disable the rich editor as I embed photo shows that don’t work otherwise. – Ashley

The first thing I do when I install WP somewhere is disable the rich text editor, the only thing I need are some XTHML shortcuts and the possibility to wrap a tag around what I’d written…I guess I’m simple.

By the way, I love it how the text field I’m writing in changes colour when I write in it, in not such a usual fashion :)

I know some people are big fans of Live Writer for posting. I keep meaning to try it, but have never gotten around to it. I don’t use the WYSIWYG either…

Christoph, you are definitely right about the testing. It was a lapse on my part that it didn’t occur to me. Andrea makes a good point, I think it is important to compartmentalise code so that it only acts when it is needed.

Di, I feel the same. I just don’t feel in control when something else is writing my code for me.

I tend to disable the Tiny MCE for my own blog, being a designer I don’t like the code some editors produce. That said Tiny is better for that than FCK. God I hated the rubbish that put out. Unfortunately I don’t have the option to disable the editor for client sites.

I use both alternately. :)

I have noticed though, that a javascript conflict in a plugin will knock that RTE right off.

For compatibilities sake TinyMCE and the built in “code” view should always be supported and tested against. FCKEditor isn’t supported by most plugins and writing in textile might be nice to be able to copy&paste between different applications/blogs, but is rarely used in WordPress.