<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Endless options mean web development does not have to hit the rails</title>
	<atom:link href="http://dharmeshmistry.wordpress.com/2008/09/26/endless-options-mean-web-development-does-not-have-to-hit-the-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://dharmeshmistry.wordpress.com/2008/09/26/endless-options-mean-web-development-does-not-have-to-hit-the-rails/</link>
	<description></description>
	<lastBuildDate>Tue, 11 Aug 2009 09:53:46 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dharmeshmistry</title>
		<link>http://dharmeshmistry.wordpress.com/2008/09/26/endless-options-mean-web-development-does-not-have-to-hit-the-rails/#comment-65</link>
		<dc:creator>dharmeshmistry</dc:creator>
		<pubDate>Sat, 14 Mar 2009 15:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=84#comment-65</guid>
		<description>Thanks, but would be good if you could expand on what you disagree with, I would certainly value an alternative opinion ;o) The template is a simple one we created internally, glad you like it and appreciate you taking time to read the blog.</description>
		<content:encoded><![CDATA[<p>Thanks, but would be good if you could expand on what you disagree with, I would certainly value an alternative opinion ;o) The template is a simple one we created internally, glad you like it and appreciate you taking time to read the blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: automotive floor jack</title>
		<link>http://dharmeshmistry.wordpress.com/2008/09/26/endless-options-mean-web-development-does-not-have-to-hit-the-rails/#comment-64</link>
		<dc:creator>automotive floor jack</dc:creator>
		<pubDate>Sat, 14 Mar 2009 12:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=84#comment-64</guid>
		<description>I have to say,   I can not agree with you in 100%, but it&#039;s just my opinion, which indeed could be   wrong.
p.s. You have a very good template  . Where have you got it from?</description>
		<content:encoded><![CDATA[<p>I have to say,   I can not agree with you in 100%, but it&#8217;s just my opinion, which indeed could be   wrong.<br />
p.s. You have a very good template  . Where have you got it from?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dharmeshmistry</title>
		<link>http://dharmeshmistry.wordpress.com/2008/09/26/endless-options-mean-web-development-does-not-have-to-hit-the-rails/#comment-24</link>
		<dc:creator>dharmeshmistry</dc:creator>
		<pubDate>Thu, 02 Oct 2008 09:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=84#comment-24</guid>
		<description>Thanks Vikas.
I agree with you ! This is a big issue. I often find also that Architects find the challenge of designing their own solution more interesting than using someone elses. However, no good architect today would advocate writing their own database, their own web server or application server. So hence they certainly should not be advocating the development of their own presentation layer, if they do, I&#039;m not sure they are the architect you want/need.

Over the coming weeks I&#039;ll be adding some more technical posts also, discussing the challenges with the presentation layer. These are too help people understand the full requirements for a presentation layer technology.

The problem today tends to be the focus is on ease, flexibility and richness of user interface development. Whilst this is important, issues such as security, performance, cross browser rendering etc... are as important if not more so. Many of these non functional requirements often get missed when selecting a presentation layer framework / technology.

regards D</description>
		<content:encoded><![CDATA[<p>Thanks Vikas.<br />
I agree with you ! This is a big issue. I often find also that Architects find the challenge of designing their own solution more interesting than using someone elses. However, no good architect today would advocate writing their own database, their own web server or application server. So hence they certainly should not be advocating the development of their own presentation layer, if they do, I&#8217;m not sure they are the architect you want/need.</p>
<p>Over the coming weeks I&#8217;ll be adding some more technical posts also, discussing the challenges with the presentation layer. These are too help people understand the full requirements for a presentation layer technology.</p>
<p>The problem today tends to be the focus is on ease, flexibility and richness of user interface development. Whilst this is important, issues such as security, performance, cross browser rendering etc&#8230; are as important if not more so. Many of these non functional requirements often get missed when selecting a presentation layer framework / technology.</p>
<p>regards D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vikas Agarwal</title>
		<link>http://dharmeshmistry.wordpress.com/2008/09/26/endless-options-mean-web-development-does-not-have-to-hit-the-rails/#comment-23</link>
		<dc:creator>Vikas Agarwal</dc:creator>
		<pubDate>Wed, 01 Oct 2008 22:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://dharmeshmistry.wordpress.com/?p=84#comment-23</guid>
		<description>Good post! However, a particular statement of yours, i.e. &quot;don’t re-invent the wheel -...&quot; does remind me of a very common problem faced at the time when a project is in its inception phase and the decision about a suitable framework is to be made. 
Given that we already have a framework available suiting pretty much each of our technical needs, we cannot always be sure that our tech architect or the responsible person is open minded and is ready to consider enough number of choices of a suitable framework. Also, this decision is made only once and its analysis may be an expensive job, leaving the tech lead/architect going ahead with what they know rather than what they might have had chosen if the decision was backed up with sufficient research.</description>
		<content:encoded><![CDATA[<p>Good post! However, a particular statement of yours, i.e. &#8220;don’t re-invent the wheel -&#8230;&#8221; does remind me of a very common problem faced at the time when a project is in its inception phase and the decision about a suitable framework is to be made.<br />
Given that we already have a framework available suiting pretty much each of our technical needs, we cannot always be sure that our tech architect or the responsible person is open minded and is ready to consider enough number of choices of a suitable framework. Also, this decision is made only once and its analysis may be an expensive job, leaving the tech lead/architect going ahead with what they know rather than what they might have had chosen if the decision was backed up with sufficient research.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
