On Wed, Sep 30, 2009 at 5:54 AM, Evan Prodromou <e...@status.net> wrote: > Brion Vibber wrote: > > On Sun, Sep 27, 2009 at 9:22 AM, Craig Andrews <candr...@integralblue.com> > wrote: >> >> I'd like to see the Twitter API be pluginized, mainly because I think it >> would be simple to do. It can be enabled by default, and just be a nice >> split from the core in terms of modularity. > > Modularity makes me feel warm and fuzzy generally... and making sure that > things _can_ be done as plugins helps to ensure that the plugin interfaces > are flexible enough. (That's been a hard lesson to learn at MediaWiki... I > think we've only _just_ made the internal interface for preferences flexible > enough that we can finish breaking out the math module to a plugin that's > been in core for like 6 years. :) > > So, I disagree here. > > I think there's a line to draw between things that can be made plugins and > things that should be made plugins.
There's a middle ground - - you can move as much as you can to plugins, but continue to ship these plugins with the core application. They're modular, so easier to debug, using the same interfaces the plugins would use -- but they're always there in every statusnet install. _______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
