WordPress as CMS?

I recently stumbled upon the article 48 Unique Ways To Use WordPress, which explains how wonderful WordPress is to use as CMS. Having had several not so good experiences with WordPress as CMS, here are the reasons why I think that this is in my opinion a bad practice:

• No flexible general purpose functions (or classes). Many WP functions return some HTML that is ready to be used, which could be ok. But there is no correct separation of the HTML markup from WP’s core functions, making the control over the generated HTML often insufficient. Many times, you end up re-writing modified versions of WP’s main functions, or writing your own SQL queries, which can break the site at every WP update!
• Inconsistent functions (or classes). The main functions are mostly consistent, but as soon as you’d like to do something a bit more advanced, you cannot rely anymore on their consistency! This creates a flat learning curve, making very hard to remember how things work.
• Badly structured and incomplete documentation. Since the functions are so inconsistent, one could hope for a good documentation. But it’s a complete wiki maze and, excepted for the most used functions, the documentation is extremely poor.
• No easy way of adding custom fields to the posts. Well, there is the meta keywords solution, but this is no user-friendly solution in most of the cases. So all you have is a title and a content, which is often not enough for slightly more complex sites!
• No absolute internal URLs saved to the database. I’ve no clue why they did that! This makes the process of moving WP from one place to another very time consuming and error prone. But it is quite common to move a site, for instance in order to work on a local copy of the site. And this is also an issue if you use WP for what is has been built for!