On Tue, Sep 29, 2009 at 9:54 AM, Evan Prodromou <[email protected]> wrote:
> Brion Vibber wrote: > > On Sun, Sep 27, 2009 at 9:22 AM, Craig Andrews > <[email protected]>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. > > I would like our core code to be a self-sufficient microblogging platform, > not a Web framework or CMS. Cutting out the API cuts down on our > functionality significantly. > > I think cutting the Twitter-like API out of core is cutting bone instead of > meat. > The API is probably a pretty extreme case, yes. :) [I might actually be more interested in having other front-end components build on the API than in modularizing the API as such, which would further support keeping it core.] -- brion
_______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
