Recently I was given the opportunity to research and implement a way to accept formatted user input that would then be displayed on a website after going through a moderation tool. In this case, the WYSIWYG was deemed the best tool for the job, as it allowed non-technical people to be able to format their input in a web-friendly way... in theory.
After much research, I was able to narrow down the best, most polished and commonly used WYSIWYG editors: TinyMCE and CKEditor. What I failed to realize at the time is that "the best WYSIWYG editor" is like saying "the best politician", in that it is the "least worse" of a flawed solution.
When using a WYSIWYG editor to perfect the formatting on your super-detailed blog entry, you'll find yourself running into a lot of little quirks. Most of them you just work around, but others can stop you dead in your tracks, forcing you to open the HTML and start hacking away on your own. This behavior is found in every WYSIWYG editor available, some more than others.
Because WYSIWYG inconsistencies are a known issue, other solutions are often used to allow users to format their input. These are different forms of markup syntax. The most popular being BBCode and Markdown. They don't come without their own set of issues as well, including but not limited to HTML cleaning/parsing issues to prevent XSS (Cross Site Scripting) attacks and educating your users on how to write using the appropriate markup script.
So when someone in your office says, "Just throw a WYSIWYG editor in there." They need to be aware of what they are proposing. My advice: Pick the solution that's right for your users. Even better, ask your users first.