I agree with your argument that native code is more stable through
upgrades than plugins. At the same time, why introduce a second
function just like one already present. If tags were to be
introduced as part of the WP core code, then categories would need to
be locked down. Mandatory one-and-only-one category per post (as
Matt mentioned, like Sections in Textpattern). If categories were
not locked down, you would essentially have the same function twice-
over with very minimal differences in functionality.
Changing the functionality in this way (one cat. per post) would
break most of the WordPress blogs currently in existence. Most, if
not all of us, have at least one post in multiple categories. I
personally don't want to go through my blog and move all that over to
a tagging function when what I've got works well and there's a plugin
out there that doesn't break anything to do what you want to do.
If you want to discipline yourself into using only one category per
post, then by all means do so, but it's not something that should be
forced upon the entire userbase. And without forcing it on the
entire userbase, all you've done is implement redundant functionality.
Nick
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
