<?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"
	>
<channel>
	<title>Comments on: Growth limits of open-source vis-a-vis MySQL Toolkit</title>
	<atom:link href="http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/</link>
	<description>Stay curious!</description>
	<pubDate>Tue, 06 Jan 2009 06:43:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Xaprb</title>
		<link>http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13655</link>
		<dc:creator>Xaprb</dc:creator>
		<pubDate>Thu, 08 Nov 2007 21:14:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13655</guid>
		<description>Hi Peter,

I think once I get finished ripping out all the copy/pasted code and replacing it with unit-tested code, releases will be very good quality.  I am pretty decent at writing tests -- I just didn't do it previously.  (again, I am not sure why).

You can contribute to sponsoring my week off work if you'd like.  I think that will be highly productive.

Help on the code is always welcome too, but I understand not everyone wants to (or can) do that.</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>I think once I get finished ripping out all the copy/pasted code and replacing it with unit-tested code, releases will be very good quality.  I am pretty decent at writing tests &#8212; I just didn&#8217;t do it previously.  (again, I am not sure why).</p>
<p>You can contribute to sponsoring my week off work if you&#8217;d like.  I think that will be highly productive.</p>
<p>Help on the code is always welcome too, but I understand not everyone wants to (or can) do that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13653</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 08 Nov 2007 20:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13653</guid>
		<description>Another option is to grow the number of people hacking on the code. I suspect with decent unit testing and good regressions, you could end up with fairly stable releases. 

That said, thanks for writing all of this! It saved me quite a bit of time over this last week. If I can help in any way, please do let me know. 

Best,

-Peter</description>
		<content:encoded><![CDATA[<p>Another option is to grow the number of people hacking on the code. I suspect with decent unit testing and good regressions, you could end up with fairly stable releases. </p>
<p>That said, thanks for writing all of this! It saved me quite a bit of time over this last week. If I can help in any way, please do let me know. </p>
<p>Best,</p>
<p>-Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fenway</title>
		<link>http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13617</link>
		<dc:creator>fenway</dc:creator>
		<pubDate>Mon, 05 Nov 2007 19:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13617</guid>
		<description>Agreed... it sounds like the platform/OS cross-dependency issues are the real deal-breaker here.</description>
		<content:encoded><![CDATA[<p>Agreed&#8230; it sounds like the platform/OS cross-dependency issues are the real deal-breaker here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xaprb</title>
		<link>http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13616</link>
		<dc:creator>Xaprb</dc:creator>
		<pubDate>Mon, 05 Nov 2007 18:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13616</guid>
		<description>I'm open to hearing what they are, but it's not getting modules included that's too much trouble in the general case.  It usually works fine.  It's when someone who doesn't know Perl well emails me saying "hi, I'm in the field with a consulting client and they have Perl 4.x running on Solaris, and I can't get this working.  I don't know Perl.  Can you help?"  I'm trying to make this easy for these folks so they don't have to ask for help.  I've had this trouble with innotop, which has a parser module that several people have had trouble getting innotop to find.  In the future innotop will be a single file, too.

Sometimes even the basic "perl Makefile.PL; make install" routine doesn't go smoothly (example: it doesn't work at all on Windows).  For that reason, my goal is that you should be able to untar the downloaded file and run it with NO installation or anything else necessary (it's just a convenience for those who want it).  I can't help it that DBI and DBD::mysql are prerequisites, but I can avoid as many other prerequisites as possible.

I gave some specific examples of what's hard for people, but in general, what's hard for people is if they're expected to understand how Perl works, so I want to shield them from it as much as possible.  That mindset may deserve criticism, but ultimately I think it makes it easier for people to benefit from the tools.</description>
		<content:encoded><![CDATA[<p>I&#8217;m open to hearing what they are, but it&#8217;s not getting modules included that&#8217;s too much trouble in the general case.  It usually works fine.  It&#8217;s when someone who doesn&#8217;t know Perl well emails me saying &#8220;hi, I&#8217;m in the field with a consulting client and they have Perl 4.x running on Solaris, and I can&#8217;t get this working.  I don&#8217;t know Perl.  Can you help?&#8221;  I&#8217;m trying to make this easy for these folks so they don&#8217;t have to ask for help.  I&#8217;ve had this trouble with innotop, which has a parser module that several people have had trouble getting innotop to find.  In the future innotop will be a single file, too.</p>
<p>Sometimes even the basic &#8220;perl Makefile.PL; make install&#8221; routine doesn&#8217;t go smoothly (example: it doesn&#8217;t work at all on Windows).  For that reason, my goal is that you should be able to untar the downloaded file and run it with NO installation or anything else necessary (it&#8217;s just a convenience for those who want it).  I can&#8217;t help it that DBI and DBD::mysql are prerequisites, but I can avoid as many other prerequisites as possible.</p>
<p>I gave some specific examples of what&#8217;s hard for people, but in general, what&#8217;s hard for people is if they&#8217;re expected to understand how Perl works, so I want to shield them from it as much as possible.  That mindset may deserve criticism, but ultimately I think it makes it easier for people to benefit from the tools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fenway</title>
		<link>http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13615</link>
		<dc:creator>fenway</dc:creator>
		<pubDate>Mon, 05 Nov 2007 18:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2007/11/05/growth-limits-of-open-source-vis-a-vis-mysql-toolkit/#comment-13615</guid>
		<description>At the risk of sounding obvious, there are a multitude of ways to get modules to be included without too much trouble... I can only assume you didn't like them, because they *do* exist.</description>
		<content:encoded><![CDATA[<p>At the risk of sounding obvious, there are a multitude of ways to get modules to be included without too much trouble&#8230; I can only assume you didn&#8217;t like them, because they *do* exist.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
