I found the Auto Tweet plugin today and have added it along with several others to the pantheon of WordPress additions that make up this blog.
WP is awesome – the plugin architecture is super cool. But there are times when I wonder why more of the plugins haven’t been made core aspects of the product itself.
The advantage of having an architecture that supports plugins is that there’s no need to add certain functionality as part of the base product as quickly. In fact, there’s no real need to do it at all unless more than a critical threshold of users install it and it becomes understood that you *have* to have the plugin to use the application.
that’s true – but there’s also the fundamental rule of never implement a “missing feature” of an application … because eventually the creators will buy/write it themselves 🙂
Are you writing a plugin to make money, or to add functionality that you feel is vital and needs to be there. If you’re not trying to pay your bills with it, then does it really matter who provides the functionality so long as it’s there? The creators making it “standard” really just becomes validation and work off your plate so you can move on to other “missing features” at that point.
I guess i’m falling back to utilities like the Notes apps that were made for iOS and then Apple supplied their own 😛