<?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: A Difficult Decision</title>
	<atom:link href="http://www.red-root.com/life/a-difficult-decision/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.red-root.com/life/a-difficult-decision/</link>
	<description>Lost in Cyberspace</description>
	<pubDate>Sat, 22 Nov 2008 06:27:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Luke</title>
		<link>http://www.red-root.com/life/a-difficult-decision/#comment-2265</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Sun, 18 Mar 2007 22:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-root.com/?p=53#comment-2265</guid>
		<description>That's fair enough, but plenty of sites which are a few years old are written in ASP, so a knowledge of it would be useful for maintenance, and it introduces a different style of programming, even if PHP and Rails are simpler. The .NET framework is currently in used, and might possibly be moreso in the future, within large businesses due to the vast variety of applications that can be linked together through it.

If luck is on our side though, PHP and Rails will become more prominent, especially according to what you are saying about displaying information. 

But I want to learn it anyway, since it's something I won't cruise through, which I would with a PHP course since by that point I'll know it pretty well.</description>
		<content:encoded><![CDATA[<p>That&#8217;s fair enough, but plenty of sites which are a few years old are written in ASP, so a knowledge of it would be useful for maintenance, and it introduces a different style of programming, even if PHP and Rails are simpler. The .NET framework is currently in used, and might possibly be moreso in the future, within large businesses due to the vast variety of applications that can be linked together through it.</p>
<p>If luck is on our side though, PHP and Rails will become more prominent, especially according to what you are saying about displaying information. </p>
<p>But I want to learn it anyway, since it&#8217;s something I won&#8217;t cruise through, which I would with a PHP course since by that point I&#8217;ll know it pretty well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.red-root.com/life/a-difficult-decision/#comment-2260</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Sun, 18 Mar 2007 16:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-root.com/?p=53#comment-2260</guid>
		<description>I spent a reasonable amount of time (at work) using ASP .NET, and I wasn't too fond of it.  One thing I can't stand, is the weight of Visual Studio -- it's completely congested and leaves you little room to work (you &lt;i&gt;have&lt;/i&gt; to put both menu's on auto hide, or you won't survive).  I found that the environment made it difficult to do exactly what I wanted at times.  For instance, in PHP and Rails, a simple loop to display information is very straightforward, and you have total control over the markup.  In .NET, it's a little more complex than it has to be, because .NET likes to throw in some unique IDs (which is another pain to keep track of when you need to do AJAXy deleting), and the CSS is hard to style because of the data grids.  I know there are ways around it, but filling an array with some data, then looping through it isn't how .NET likes to do things.  Working in the HTML becomes very messy, very quickly, which I despise.

In the end, I don't have much experience with .NET to fully details it's pros and cons.  It's going to be a personal choice obviously, but I've found that I'm more drawn to simplicity these days.</description>
		<content:encoded><![CDATA[<p>I spent a reasonable amount of time (at work) using ASP .NET, and I wasn&#8217;t too fond of it.  One thing I can&#8217;t stand, is the weight of Visual Studio &#8212; it&#8217;s completely congested and leaves you little room to work (you <i>have</i> to put both menu&#8217;s on auto hide, or you won&#8217;t survive).  I found that the environment made it difficult to do exactly what I wanted at times.  For instance, in PHP and Rails, a simple loop to display information is very straightforward, and you have total control over the markup.  In .NET, it&#8217;s a little more complex than it has to be, because .NET likes to throw in some unique IDs (which is another pain to keep track of when you need to do AJAXy deleting), and the CSS is hard to style because of the data grids.  I know there are ways around it, but filling an array with some data, then looping through it isn&#8217;t how .NET likes to do things.  Working in the HTML becomes very messy, very quickly, which I despise.</p>
<p>In the end, I don&#8217;t have much experience with .NET to fully details it&#8217;s pros and cons.  It&#8217;s going to be a personal choice obviously, but I&#8217;ve found that I&#8217;m more drawn to simplicity these days.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
