<?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: Questions on Rails for prototyping</title>
	<atom:link href="http://justaddwater.dk/2006/04/22/questions-rails-prototyping/feed/" rel="self" type="application/rss+xml" />
	<link>http://justaddwater.dk/2006/04/22/questions-rails-prototyping/</link>
	<description>Instant Usability &#38; Web Standards</description>
	<lastBuildDate>Sat, 28 Jan 2012 13:44:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Thomas Watson Steen</title>
		<link>http://justaddwater.dk/2006/04/22/questions-rails-prototyping/comment-page-1/#comment-2383</link>
		<dc:creator>Thomas Watson Steen</dc:creator>
		<pubDate>Mon, 24 Apr 2006 18:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/04/22/questions-rails-prototyping/#comment-2383</guid>
		<description>Hi Luis

Nice to see that you are still following our blog. Jesper is enjoying a nice long vacation in Italy, so I&#039;m gonna answer instead :)

&lt;blockquote&gt;[...] But I insist… what’s left for RoR to jump in the main scene?[...]&lt;/blockquote&gt;
Nothing technical - Maybe only a bid of costumer lobbying – that’s it. We are in Capgemini definitely looking to use Ruby on Rails in production and not only for prototyping. I know for a fact that one of our prototypes is going to be in production as soon as it has been polished. I&#039;m sure we are gonna write more about that as the project develops :)

&lt;blockquote&gt;[...] What do developers think? Are you sure is just for prototyping? ;-)&lt;/blockquote&gt;
As a developer I&#039;m very exited about RoR, both for prototyping but certainly also for production. It&#039;s not that much RoR but the framework (and to some extend the power of the Ruby language) that excites me. But I&#039;m sure that another framework could be built in another language giving the developer the same benefits. Just as long as it was a language as powerful as Ruby.

Our goal is to tell our managers, our sales people and our costumers about the power of RoR. This can&#039;t always be done in one strike. We think that the easies way to do this is to first show how easy it is to build prototypes and bring down the documentation costs. If we do this well (and it certainly looks like that we are), then we will very quickly get peoples attention and they will be asking for more. Then we can start using Ruby on Rails from start till finish :)</description>
		<content:encoded><![CDATA[<p>Hi Luis</p>
<p>Nice to see that you are still following our blog. Jesper is enjoying a nice long vacation in Italy, so I&#8217;m gonna answer instead :)</p>
<blockquote><p>[...] But I insist… what’s left for RoR to jump in the main scene?[...]</p></blockquote>
<p>Nothing technical &#8211; Maybe only a bid of costumer lobbying – that’s it. We are in Capgemini definitely looking to use Ruby on Rails in production and not only for prototyping. I know for a fact that one of our prototypes is going to be in production as soon as it has been polished. I&#8217;m sure we are gonna write more about that as the project develops :)</p>
<blockquote><p>[...] What do developers think? Are you sure is just for prototyping? ;-)</p></blockquote>
<p>As a developer I&#8217;m very exited about RoR, both for prototyping but certainly also for production. It&#8217;s not that much RoR but the framework (and to some extend the power of the Ruby language) that excites me. But I&#8217;m sure that another framework could be built in another language giving the developer the same benefits. Just as long as it was a language as powerful as Ruby.</p>
<p>Our goal is to tell our managers, our sales people and our costumers about the power of RoR. This can&#8217;t always be done in one strike. We think that the easies way to do this is to first show how easy it is to build prototypes and bring down the documentation costs. If we do this well (and it certainly looks like that we are), then we will very quickly get peoples attention and they will be asking for more. Then we can start using Ruby on Rails from start till finish :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Villa</title>
		<link>http://justaddwater.dk/2006/04/22/questions-rails-prototyping/comment-page-1/#comment-2382</link>
		<dc:creator>Luis Villa</dc:creator>
		<pubDate>Mon, 24 Apr 2006 15:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://justaddwater.dk/2006/04/22/questions-rails-prototyping/#comment-2382</guid>
		<description>Hi Jesper... I agree with your points... I was playing the devil&#039;s advocate... ;-) But I insist... what&#039;s left for RoR to jump in the main scene? Could it be possible going live with the RoR prototype finished version instead of jumping from RoR to Java? 

What do developers think? Are you sure is just for prototyping? ;-)</description>
		<content:encoded><![CDATA[<p>Hi Jesper&#8230; I agree with your points&#8230; I was playing the devil&#8217;s advocate&#8230; ;-) But I insist&#8230; what&#8217;s left for RoR to jump in the main scene? Could it be possible going live with the RoR prototype finished version instead of jumping from RoR to Java? </p>
<p>What do developers think? Are you sure is just for prototyping? ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

