hi,
here hicks compares ee with textpattern. i myself use ee for now 3 (?) years, and i could sign everything, regarding the advantages and the disadvantages (except statistics - i love and need them!). i quote the disadvantages:
**** My biggest beef with EE is the admin panel. I find it needlessly complicated, with options hidden behind many overly-wordy, illogical links and dropdowns. While a certain amount of this is inevitable with the level of control that it offers, it’s certainly more painful than it needs to be. The longer I have to look at it, the angrier I get!
**** EE promotes itself as a CMS, rather than blogging tool, yet out of the box it insists on referring to ‘weblogs’. This can be changed through one of many preferences to something more logical like ‘section’, but the template tags will still refer to weblogs. Harumph.
**** /index.php/ shouldn’t be in URLs by default, and it’s right pain to get rid of (but you can do it). Likewise, getting simple /section/title/ urls requires a lot of work. For something so flexible, getting the URLs I want is painful. With a new site this isn’t so bad, you can put up with the extra URL segment, but when converting a site from TXP, and not wanting to write large .htaccess redirections, it’s vital.
**** EE seems obsessed with statistics, time taken to render page etc. It’s all superflous fluff. Generally, I’m left with the feeling of “I wish I could just get rid of this bit here…”
**** A smaller rant, I’m none too keen on the tags: some require exp: at the start, some don’t.
**** File management is behind Textpattern, which has more control over uploaded images and files. This really surprised me! There is a good file manager plugin for EE, but this review is looking at built-in functionality.
taken from:
http://www.hicksdesign.co.uk/journal/expression-engine-vs-textpattern
