<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Ironboy is coming soon</title>
	<atom:link href="http://mdk.per.ly/2010/03/09/ironboy-is-coming-soon/feed/" rel="self" type="application/rss+xml" />
	<link>http://mdk.per.ly/2010/03/09/ironboy-is-coming-soon/</link>
	<description>A per.ly perl weblog by Mark Keating</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:27:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: mdk</title>
		<link>http://mdk.per.ly/2010/03/09/ironboy-is-coming-soon/comment-page-1/#comment-1251</link>
		<dc:creator>mdk</dc:creator>
		<pubDate>Wed, 17 Mar 2010 13:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://mdk.per.ly/?p=439#comment-1251</guid>
		<description>Hi Phillip. The main issues with Plagger that I was aware of during the choice to move were mostly to do with flexibility and size. Plagger installs a number of dependencies and we were concerned about the size as it was making Plagger a little inflexible and we needed to bring some flexibility into the system as we were moving towards integrating into a Catalyst framework for future development. Perlanet allowed us to use a system that was smaller and more mutable for fitting into the architectural choices we were making. I would say that if you pop into the #northwestengland.pm channel on irc.perl.org you&#039;ll get a better understanding of some of the issues if you speak to Carl (fade), Ian (idn) and Matt (mst).</description>
		<content:encoded><![CDATA[<p>Hi Phillip. The main issues with Plagger that I was aware of during the choice to move were mostly to do with flexibility and size. Plagger installs a number of dependencies and we were concerned about the size as it was making Plagger a little inflexible and we needed to bring some flexibility into the system as we were moving towards integrating into a Catalyst framework for future development. Perlanet allowed us to use a system that was smaller and more mutable for fitting into the architectural choices we were making. I would say that if you pop into the #northwestengland.pm channel on irc.perl.org you&#8217;ll get a better understanding of some of the issues if you speak to Carl (fade), Ian (idn) and Matt (mst).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Smith</title>
		<link>http://mdk.per.ly/2010/03/09/ironboy-is-coming-soon/comment-page-1/#comment-1240</link>
		<dc:creator>Phillip Smith</dc:creator>
		<pubDate>Mon, 15 Mar 2010 21:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://mdk.per.ly/?p=439#comment-1240</guid>
		<description>Just wondering if you can expand on the thinking behind Perlanet vs. Plagger? As someone who&#039;s only poked around with Plagger, I&#039;m curious about what the trade-offs are? 

Phillip.</description>
		<content:encoded><![CDATA[<p>Just wondering if you can expand on the thinking behind Perlanet vs. Plagger? As someone who&#8217;s only poked around with Plagger, I&#8217;m curious about what the trade-offs are? </p>
<p>Phillip.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

