[wp-trac] Re: [WordPress Trac] #4547: Convert WP from magpie to
Simplepie
WordPress Trac
wp-trac at lists.automattic.com
Mon Jul 2 15:10:27 GMT 2007
#4547: Convert WP from magpie to Simplepie
----------------------------------+-----------------------------------------
Reporter: technosailor | Owner: technosailor
Type: task | Status: new
Priority: normal | Milestone: 2.3 (trunk)
Component: General | Version: 2.3
Severity: normal | Resolution:
Keywords: simplepie magpie rss |
----------------------------------+-----------------------------------------
Comment (by technosailor):
As far as I can tell, the only one opposing this is Matt. It seems a bit
like tags in 2.2. Matt, I don't know if you're just playing devil's
advocate but either way, you're outnumbered.
My argument is much more philisophical. Otto makes a good case for the
technical and practical side of the argument. However, from where I sit,
feeds are becoming more about ubiquitous content. We don't know when,
where, how or why content is being used and in what form it's being used.
WP has done a good job of providing it's own content in a variety of
formats. The reality is WP is also on the consuming side of content and we
are bottlenecked right now. Plugin authors can't write plugins to do feed
consummation effectively unless they bundle their own feed library and
that on it's face is just silly when we already provide a library. Why
should a plugin author have to bundle SimplePie when WP is offering
Magpie? Quite simply, magpie sucks and by bundling both... well again,
that's just silly.
WP should be offering Simplepie because
1) It's better than Magpie
2) It makes it easier for plugin authors to write RSS-consuming plugins
3) It meets the "Code is Poetry" mantra of WP by providing clean and
simple functions to do all the stuff a library should do. Magpie is just
fugly.
4) Upgrading Simplepie is as clean as dropping an upgraded library into
class-Simplepie.php. No fuss, no muss, no editing. Matt, why is upgrading
hard?
5) Provides WP a future-proofed method of consuming feeds in new and
different ways not yet in this iteration of WP.
6) Because feed consumption in a blogging software should not be relegated
to "second rate" functionality or as additional pieces of flair. Feed
consumption is _essential_ to blogging and blogging software. Let's stop
rying to pretend it can be worked around.
--
Ticket URL: <http://trac.wordpress.org/ticket/4547#comment:20>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list