<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2011/12/25/shortform</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2011/12/25/shortform"/><id>http://norman.walsh.name/2011/12/25/shortform/comments.atom</id><updated>2012-05-24T00:08:54.120203Z</updated><entry><title>Comment 1 on /2011/12/25/shortform</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2011/12/25/shortform#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2012-01-02T19:36:45Z</published><updated>2012-01-02T19:36:45Z</updated><author><name>Aristotle Pagaltzis</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>As for Net::Twitter, see <a href="http://www.jwz.org/blog/2011/04/a-badge-for-the-software-industrys-failures/#comment-90218">
Chris Thompon’s comment on jwz’s complaint about it</a>: the
((only) somewhat) surprising explanation is that Twitter’s API is
inconsistent and ever-changing… which has to be managed somehow by
bindings authors.</p></div></content></entry></feed>

