<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>has_many :thoughts: .rhtml deprecated?</title>
    <link>http://blog.kineticweb.com/articles/2007/05/07/rhtml-deprecated</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Musings from a Ruby on Rails development team</description>
    <item>
      <title>.rhtml deprecated?</title>
      <description>&lt;p&gt;I don&amp;#8217;t know why I didn&amp;#8217;t learn of this until now. But &lt;a href="http://dev.rubyonrails.org/changeset/6178"&gt;.rhtml file extensions are now deprecated&lt;/a&gt; and will be removed at some point. One is supposed to use .erb instead of .rhtml.&lt;/p&gt;


	&lt;p&gt;On one hand, it bugs me that a lot of stuff deprecates pretty frequently with Rails. Seems like there&amp;#8217;s always some warning that&amp;#8217;s popping up in the Mongrel console window.&lt;/p&gt;


	&lt;p&gt;On the other hand, so far, it&amp;#8217;s been pretty trivial to change over to the new conventions and clear up deprecation warnings. And I have yet to see functionality actually drop off so it&amp;#8217;s not like I&amp;#8217;m not given plenty of notice.&lt;/p&gt;


	&lt;p&gt;Of course, with the way Gems work, I can have different versions of Rails running on the same machine with is &lt;em&gt;awesome&lt;/em&gt;. Because, as a contract development shop, sometimes clients just aren&amp;#8217;t going to pay to upgrade an app to the latest version of whatever. And those clients can remain running on old Rails versions as long as they want while the rest of the sites run the latest versions.&lt;/p&gt;</description>
      <pubDate>Mon, 07 May 2007 10:08:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:2df051f8-dc72-4d93-b975-f34ce763146a</guid>
      <author>Colin A. Bartlett</author>
      <link>http://blog.kineticweb.com/articles/2007/05/07/rhtml-deprecated</link>
      <category>Rails</category>
    </item>
    <item>
      <title>".rhtml deprecated?" by Justin Reagor</title>
      <description>In actuality I think this makes a lot more sense. It goes with the RESTful approach of designing web apps... in the web of the future, I do not believe you will be designing apps for straight off HTML browsers, but other data aggregators as well. Such as RSS/Atom feeds, XML data transfers, JSON usage, templates for emailing, etc... etc... .rhtml kind of singles that out.

Of course it does not matter what the file extension is, its just that, a file extension! Though, that seems to be a really linux/unix user type thing to say... :)

Your right on the deprecation stuff, Rails keeps us on our toes. Though thats also a good thing, to know that Rails keeps us up-to-date on things and not settled into some comforting spider hole. At least we won't have to worry about converting all these file names, into .erb or whatever, until Rails 3.0...

PS: Don't think that this will stick, as we have had major changes swapped back like REST's "http://localhost/controller/action;edit" which was switched back to "action/edit" I believe.</description>
      <pubDate>Mon, 07 May 2007 20:40:27 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:49c7956e-0bb1-421f-85a8-7e98d1ba60ac</guid>
      <link>http://blog.kineticweb.com/articles/2007/05/07/rhtml-deprecated#comment-3</link>
    </item>
  </channel>
</rss>
