[wp-hackers] This was painful to read...

Thomas Belknap dragonfly at dragonflyeye.net
Sat Nov 28 12:21:17 UTC 2009

I can get behind the URL routing issues. I can get behind supporting
slightly more abstraction to the data structure of WordPress for the sake of
greater flexibility. But it *is* WORDpress, not PDFpress or EvaluationPress.
The assumption has always been that WordPress is a blog - or if you prefer
not to use that term, a "self publication tool." - not a CMS. For those
willing to put a bunch of extra work into building a full-fledged CMS out of
WP, I say good luck. But I prefer my tools to be good at what they do, not
half-assed for the sake of being like other software that is already out
there in an already saturated market.

WordPress installs easy, sets up fast and is hugely flexible for those
looking to publish their words on the Internet. Those who think the same is
true for Drupal have forgotten what it's like not to know how to do what we
do here. This ease of use factor is what gives WP it's market share.
Changing it will doubtless have the opposite effect.

On Sat, Nov 28, 2009 at 7:02 AM, Mike Schinkel
<mikeschinkel at newclarity.net>wrote:

> This was painful to read. Not because I disagree, but because I can't
> disagree even though I wish it were not true:
> From: http://birdhouse.org/blog/2009/11/11/drupal-or-django/
> "For example, it makes sense to build student magazines, handbooks, FAQs,
> and blogs with WordPress. But it’s simply not possible to build an equipment
> checkout system, or a course evaluation system, or a student/faculty/staff
> directory with WordPress — not while trying to preserve your sanity. That’s
> because WordPress assumes so much about the structure of your data — it
> thinks every piece of content has a title, a summary, an author, etc. Start
> to veer away from that basic data structure and you find yourself quickly
> needing a platform that doesn’t make assumptions about how things should be
> done. For those kinds of problems, we use Django."
> At least for me, this is the crux of my issues with URL routing; WordPress
> wants to force me to use a certain URL structure that doesn't fit many use
> cases when it would be so easy to have WordPress handle URL routing more
> generically. If the difficulty in URL routing could be fixed, most
> everything else would be easy to fix.
> -Mike Schinkel
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list