<?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: Calculating Hashes of Strings and Files</title>
	<atom:link href="http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/feed/" rel="self" type="application/rss+xml" />
	<link>http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/</link>
	<description></description>
	<pubDate>Sat, 10 May 2008 22:10:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Matthew Weier O'Phinney</title>
		<link>http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/#comment-110</link>
		<dc:creator>Matthew Weier O'Phinney</dc:creator>
		<pubDate>Fri, 29 Feb 2008 17:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/#comment-110</guid>
		<description>Learning another language can also inform you about areas of your language of expertise that you may not have been aware of. For instance, in learning about hashing algorithms in Ruby, you may stumble across the fact that PHP 5 has added a 'hash' extension that does general purpose hashing using a variety of algorithms (and that md5() and sha1() are no longer the only ways of hashing using those algorithms, and the extension adds a ton more possibilities for hashing).

Learning another language also can show you areas in your language of expertise that could be improved. You note Ruby closures, for example -- PHP does not have closures (create_function() is a bear to work with, in comparison). Would you like them in PHP? Do they make sense for PHP?

I've found learning another language helps make my usage of my language of proficiency -- PHP -- stronger and more efficient. It's not necessarily a question of one being better than the other -- it's a question of learning the various tools available -- including other languages -- and how to wield them effectively.</description>
		<content:encoded><![CDATA[<p>Learning another language can also inform you about areas of your language of expertise that you may not have been aware of. For instance, in learning about hashing algorithms in Ruby, you may stumble across the fact that PHP 5 has added a &#8216;hash&#8217; extension that does general purpose hashing using a variety of algorithms (and that md5() and sha1() are no longer the only ways of hashing using those algorithms, and the extension adds a ton more possibilities for hashing).</p>
<p>Learning another language also can show you areas in your language of expertise that could be improved. You note Ruby closures, for example &#8212; PHP does not have closures (create_function() is a bear to work with, in comparison). Would you like them in PHP? Do they make sense for PHP?</p>
<p>I&#8217;ve found learning another language helps make my usage of my language of proficiency &#8212; PHP &#8212; stronger and more efficient. It&#8217;s not necessarily a question of one being better than the other &#8212; it&#8217;s a question of learning the various tools available &#8212; including other languages &#8212; and how to wield them effectively.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/#comment-109</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 29 Feb 2008 17:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/#comment-109</guid>
		<description>As you see many more of these examples, sometimes you're going to feel like PHP comes out ahead and sometimes you'll feel like Ruby does.  It sounds like you're pretty open minded, and that's great.  People that are  polarized completely one way or another just aren't being objective.  

We spent a lot of time in the book talking about where we think Ruby and Rails shine, without trying to be over the top about it. We'll continue to do that here in future articles.  We definitely like Ruby a lot, and Rails works very well for many of the things we need to do.  Many, but certainly not all.  

Whether you'll like Ruby or Rails depends mostly on your needs and how well they fit into them. It's very situational. We can't really say "these are the reasons you'll love Ruby". All we can do is be positive and objective, and let you learn and figure out what works for you. One thing that's for sure is Ruby certainly isn't a replacement for PHP, that PHP isn't a replacement for Ruby, and there's quite a bit of  overlap.

I hope that you'll keep reading our future articles as we get deeper into
these topics, have some fun experimenting with Ruby, and continue to build an informed opinion.</description>
		<content:encoded><![CDATA[<p>As you see many more of these examples, sometimes you&#8217;re going to feel like PHP comes out ahead and sometimes you&#8217;ll feel like Ruby does.  It sounds like you&#8217;re pretty open minded, and that&#8217;s great.  People that are  polarized completely one way or another just aren&#8217;t being objective.  </p>
<p>We spent a lot of time in the book talking about where we think Ruby and Rails shine, without trying to be over the top about it. We&#8217;ll continue to do that here in future articles.  We definitely like Ruby a lot, and Rails works very well for many of the things we need to do.  Many, but certainly not all.  </p>
<p>Whether you&#8217;ll like Ruby or Rails depends mostly on your needs and how well they fit into them. It&#8217;s very situational. We can&#8217;t really say &#8220;these are the reasons you&#8217;ll love Ruby&#8221;. All we can do is be positive and objective, and let you learn and figure out what works for you. One thing that&#8217;s for sure is Ruby certainly isn&#8217;t a replacement for PHP, that PHP isn&#8217;t a replacement for Ruby, and there&#8217;s quite a bit of  overlap.</p>
<p>I hope that you&#8217;ll keep reading our future articles as we get deeper into<br />
these topics, have some fun experimenting with Ruby, and continue to build an informed opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lifewithryan</title>
		<link>http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/#comment-108</link>
		<dc:creator>lifewithryan</dc:creator>
		<pubDate>Fri, 29 Feb 2008 15:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://railsforphp.com/2008/02/26/calculating-string-and-file-hashes/#comment-108</guid>
		<description>Just curious, as this is my first time seeing such comparisons...but is it just me or does PHP seem to do the same things, with less code?

Not that "less code" is necessarily better or anything but what does ruby/rails buy me over PHP/CodeIgniter/Cake, insert php framework here?

You always hear the code comparisons between Rails and other frameworks in lines of code, etc...this doesn't seem to be any more efficient.

(Granted the closures save alot of lines of code and we're not seeing that here...just a question...)</description>
		<content:encoded><![CDATA[<p>Just curious, as this is my first time seeing such comparisons&#8230;but is it just me or does PHP seem to do the same things, with less code?</p>
<p>Not that &#8220;less code&#8221; is necessarily better or anything but what does ruby/rails buy me over PHP/CodeIgniter/Cake, insert php framework here?</p>
<p>You always hear the code comparisons between Rails and other frameworks in lines of code, etc&#8230;this doesn&#8217;t seem to be any more efficient.</p>
<p>(Granted the closures save alot of lines of code and we&#8217;re not seeing that here&#8230;just a question&#8230;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 2.825 seconds -->
