The code editor. One for plugins and one for themes. If I were using tracking software, it would register me as rarely venturing into that part of the WordPress administration. I’ve used WordPress for two years and I’ve burned myself enough times by using these code editors that I neglect to use them anymore side from looking but not touching code. The biggest problem I have is that it doesn’t contain any revisions. Also, when you click the save button, it reloads the page and causes the scroll bar in the code window to go back to the top meaning I have to remember which line of code I was editing and also remember the change I implemented so I can remove it if I don’t like the desired effects.
I’ve really come to appreciate using Control Z on my keyboard to undo changes I don’t like. You can’t do a Control Z after you click the save button in the editor which again, brings me back to my complaint of no revisions. When CodePress was introduced, I thought it was cool and a much-needed upgrade over the current implementation. However, I love NotePad++ and the ability to play around with a local copy of my site by editing the files directly within a good editor instead of through WordPress.
It’s my opinion that those who know what they are doing use their favorite tool and then upload the changes rather than the built-in code editor. I’m going to take a guess and say that end users make up the majority of the user base for WordPress and that this user base is not so inclined to use the editor to change code around. Therefor, I’m hoping to hear some valid reasons as to why it should be kept in WordPress.