<?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 for Patrick Tulskie</title>
	<atom:link href="http://www.patricktulskie.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.patricktulskie.com</link>
	<description>Building a Better Internet</description>
	<lastBuildDate>Wed, 09 Dec 2009 23:09:41 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on libxml-ruby vs nokogiri vs hpricot by Patrick Tulskie</title>
		<link>http://www.patricktulskie.com/2009/03/libxml-ruby-vs-nokogiri-vs-hpricot/comment-page-1/#comment-103</link>
		<dc:creator>Patrick Tulskie</dc:creator>
		<pubDate>Wed, 09 Dec 2009 23:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=115#comment-103</guid>
		<description>No problem.  Glad you found it useful.</description>
		<content:encoded><![CDATA[<p>No problem.  Glad you found it useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Code Highlighting by Patrick Tulskie</title>
		<link>http://www.patricktulskie.com/2009/12/code-highlighting/comment-page-1/#comment-102</link>
		<dc:creator>Patrick Tulskie</dc:creator>
		<pubDate>Wed, 09 Dec 2009 23:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=132#comment-102</guid>
		<description>Yep. Could do that too. Probably should do that, in the spirit of social coding.</description>
		<content:encoded><![CDATA[<p>Yep. Could do that too. Probably should do that, in the spirit of social coding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Code Highlighting by Jason Amster</title>
		<link>http://www.patricktulskie.com/2009/12/code-highlighting/comment-page-1/#comment-101</link>
		<dc:creator>Jason Amster</dc:creator>
		<pubDate>Wed, 09 Dec 2009 23:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=132#comment-101</guid>
		<description>Uh, why not just use embed a Gist. e.g. http://blog.jayamster.com/a-little-snippit-to-tell-if-its-unix-time-1234567890/2009/02/13</description>
		<content:encoded><![CDATA[<p>Uh, why not just use embed a Gist. e.g. <a href="http://blog.jayamster.com/a-little-snippit-to-tell-if-its-unix-time-1234567890/2009/02/13" rel="nofollow">http://blog.jayamster.com/a-little-snippit-to-tell-if-its-unix-time-1234567890/2009/02/13</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WebbyNode, Nginx, and Percona MySQL by Patrick Tulskie</title>
		<link>http://www.patricktulskie.com/2009/12/webbynode-nginx-percona-mysql/comment-page-1/#comment-99</link>
		<dc:creator>Patrick Tulskie</dc:creator>
		<pubDate>Wed, 09 Dec 2009 18:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=128#comment-99</guid>
		<description>I&#039;m not using it yet, but I will be. I&#039;ve heard it handles load relatively well, but I don&#039;t anticipate anything I&#039;m going to be using it for to be under any heavy load.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not using it yet, but I will be. I&#8217;ve heard it handles load relatively well, but I don&#8217;t anticipate anything I&#8217;m going to be using it for to be under any heavy load.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WebbyNode, Nginx, and Percona MySQL by Travis</title>
		<link>http://www.patricktulskie.com/2009/12/webbynode-nginx-percona-mysql/comment-page-1/#comment-97</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:24:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=128#comment-97</guid>
		<description>Are you actively using Unicorn? I&#039;ve heard some mixed things about it and how well it performs under a load.</description>
		<content:encoded><![CDATA[<p>Are you actively using Unicorn? I&#8217;ve heard some mixed things about it and how well it performs under a load.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby String#Nameize Revised by Patrick Tulskie</title>
		<link>http://www.patricktulskie.com/2008/12/ruby-string-nameize-revised/comment-page-1/#comment-96</link>
		<dc:creator>Patrick Tulskie</dc:creator>
		<pubDate>Sun, 20 Sep 2009 23:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=102#comment-96</guid>
		<description>Thanks for that raggi.  Great set of tweaks.  Yeah I&#039;ve come to learn a great deal since I originally wrote this dirty code.  Case has been one of those things I&#039;ve stopped abusing such as you saw before.  I&#039;m glad that people are still finding this useful and improving upon it.  As you&#039;ll probably notice, I&#039;ve stopped writing on my blog as much and have been reading through the code of others&#039; as of late.</description>
		<content:encoded><![CDATA[<p>Thanks for that raggi.  Great set of tweaks.  Yeah I&#8217;ve come to learn a great deal since I originally wrote this dirty code.  Case has been one of those things I&#8217;ve stopped abusing such as you saw before.  I&#8217;m glad that people are still finding this useful and improving upon it.  As you&#8217;ll probably notice, I&#8217;ve stopped writing on my blog as much and have been reading through the code of others&#8217; as of late.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby String#Nameize Revised by raggi</title>
		<link>http://www.patricktulskie.com/2008/12/ruby-string-nameize-revised/comment-page-1/#comment-95</link>
		<dc:creator>raggi</dc:creator>
		<pubDate>Thu, 10 Sep 2009 16:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=102#comment-95</guid>
		<description>I can see where you&#039;re trying to apply &quot;performance optimizations&quot; but they&#039;re introducing bugs, that you don&#039;t seem to have benchmark, profile, or test coverage for.

You don&#039;t need gsub with a regex of /^ ... /

You could do the entire sub line operation in a single sub, and probably should do. Sub isn&#039;t delete, afterall. Oh, and the two sub cases are equivalent, with a different first group.

Stop using String#match without utilising the match data, and for that matter, use case properly, rather than this new way you&#039;ve learned.

Oh screw it... here comes codes...

&lt;em&gt;
&lt;code&gt;
class String
  SPACE = &#039; &#039;
  APOS = &quot;&#039;&quot;

  # Extension of the string class to properly handle camel names
  def nameize
    case self
    when / /
      # If the name has a space in it, we gotta run the parts through the nameizer.
      split(SPACE).each { &#124;part&#124; part.nameize! }.join(SPACE)
    when /^[A-Z]/
      # If they took the time to capitalize their name then let&#039;s just jump out.
      self
    when /^(mac&#124;mc)(\w)(.*)$/i
      &quot;#{$1.capitalize}#{$2.capitalize}#{$3}&quot;
    when /^o\&#039;/i
      split(APOS).each{ &#124;piece&#124; piece.capitalize! }.join(APOS)
    else
      capitalize # Basically if the name is a first name or it&#039;s not Irish then capitalize it.
    end
  end

  def nameize!
    replace nameize # BANG!
  end

end

require &#039;rubygems&#039;
require &#039;minitest/unit&#039;
include MiniTest::Assertions
assert_equal(&quot;Martin O&#039;Donald&quot;, &quot;martin o&#039;donald&quot;.nameize)
assert_equal(&quot;Randy McFarley&quot;, &quot;Randy mcfarley&quot;.nameize)
assert_equal(&quot;Sue MacDonald&quot;, &quot;sue macdonald&quot;.nameize)
&lt;/code&gt;
&lt;/em&gt;

Have fun, and play safe.</description>
		<content:encoded><![CDATA[<p>I can see where you&#8217;re trying to apply &#8220;performance optimizations&#8221; but they&#8217;re introducing bugs, that you don&#8217;t seem to have benchmark, profile, or test coverage for.</p>
<p>You don&#8217;t need gsub with a regex of /^ &#8230; /</p>
<p>You could do the entire sub line operation in a single sub, and probably should do. Sub isn&#8217;t delete, afterall. Oh, and the two sub cases are equivalent, with a different first group.</p>
<p>Stop using String#match without utilising the match data, and for that matter, use case properly, rather than this new way you&#8217;ve learned.</p>
<p>Oh screw it&#8230; here comes codes&#8230;</p>
<p><em><br />
<code><br />
class String<br />
  SPACE = ' '<br />
  APOS = "'"</p>
<p>  # Extension of the string class to properly handle camel names<br />
  def nameize<br />
    case self<br />
    when / /<br />
      # If the name has a space in it, we gotta run the parts through the nameizer.<br />
      split(SPACE).each { |part| part.nameize! }.join(SPACE)<br />
    when /^[A-Z]/<br />
      # If they took the time to capitalize their name then let's just jump out.<br />
      self<br />
    when /^(mac|mc)(\w)(.*)$/i<br />
      "#{$1.capitalize}#{$2.capitalize}#{$3}"<br />
    when /^o\'/i<br />
      split(APOS).each{ |piece| piece.capitalize! }.join(APOS)<br />
    else<br />
      capitalize # Basically if the name is a first name or it's not Irish then capitalize it.<br />
    end<br />
  end</p>
<p>  def nameize!<br />
    replace nameize # BANG!<br />
  end</p>
<p>end</p>
<p>require 'rubygems'<br />
require 'minitest/unit'<br />
include MiniTest::Assertions<br />
assert_equal("Martin O'Donald", "martin o'donald".nameize)<br />
assert_equal("Randy McFarley", "Randy mcfarley".nameize)<br />
assert_equal("Sue MacDonald", "sue macdonald".nameize)<br />
</code><br />
</em></p>
<p>Have fun, and play safe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby String#Nameize Revised by Brookr</title>
		<link>http://www.patricktulskie.com/2008/12/ruby-string-nameize-revised/comment-page-1/#comment-94</link>
		<dc:creator>Brookr</dc:creator>
		<pubDate>Fri, 28 Aug 2009 06:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=102#comment-94</guid>
		<description>Thanks for sharing this, just what I needed!</description>
		<content:encoded><![CDATA[<p>Thanks for sharing this, just what I needed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on libxml-ruby vs nokogiri vs hpricot by JamesD</title>
		<link>http://www.patricktulskie.com/2009/03/libxml-ruby-vs-nokogiri-vs-hpricot/comment-page-1/#comment-93</link>
		<dc:creator>JamesD</dc:creator>
		<pubDate>Thu, 11 Jun 2009 17:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=115#comment-93</guid>
		<description>Thanks for the useful info. It&#039;s so interesting</description>
		<content:encoded><![CDATA[<p>Thanks for the useful info. It&#8217;s so interesting</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Leopard and MySQL Gem by Nick Rudzwick</title>
		<link>http://www.patricktulskie.com/2008/11/leopard-and-mysql-gem/comment-page-1/#comment-62</link>
		<dc:creator>Nick Rudzwick</dc:creator>
		<pubDate>Mon, 09 Mar 2009 18:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.patricktulskie.com/?p=88#comment-62</guid>
		<description>Dude, that is a keeper!

It took a little bit more to get mine working, with Patrick&#039;s help!

1. make a bash_login file 
2. stick this in it:

export PATH=&quot;$PATH:/usr/local/mysql/bin&quot;

3. save it
4. open a new terminal window
5. Lastly, type this in terminal:

ARCHFLAGS=&quot;-arch i386&quot; sudo gem install mysql -- --with-mysql-config</description>
		<content:encoded><![CDATA[<p>Dude, that is a keeper!</p>
<p>It took a little bit more to get mine working, with Patrick&#8217;s help!</p>
<p>1. make a bash_login file<br />
2. stick this in it:</p>
<p>export PATH=&#8221;$PATH:/usr/local/mysql/bin&#8221;</p>
<p>3. save it<br />
4. open a new terminal window<br />
5. Lastly, type this in terminal:</p>
<p>ARCHFLAGS=&#8221;-arch i386&#8243; sudo gem install mysql &#8212; &#8211;with-mysql-config</p>
]]></content:encoded>
	</item>
</channel>
</rss>
