<?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: look, my name&#8217;s in the news!</title>
	<atom:link href="http://dossy.org/2005/01/look-my-names-in-the-news/feed/" rel="self" type="application/rss+xml" />
	<link>http://dossy.org/2005/01/look-my-names-in-the-news/</link>
	<description>Everything that comes out of Dossy, from the strange to the banal.</description>
	<lastBuildDate>Wed, 16 May 2012 14:29:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Dossy</title>
		<link>http://dossy.org/2005/01/look-my-names-in-the-news/comment-page-1/#comment-74</link>
		<dc:creator>Dossy</dc:creator>
		<pubDate>Sun, 23 Jan 2005 13:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://dossy.org/archives/000084.html#comment-74</guid>
		<description>Joe Grossberg commented in &lt;a href=&quot;http://www.livejournal.com/users/dossy/5666.html&quot;&gt;my LiveJournal&lt;/a&gt;:

&lt;blockquote&gt;Wow, someone&#039;s still using Tcl ... having dabbled in Expect and Tcl/Tk ... I can say that the support for other languages is key to growing its user and developer bases. I know it&#039;s shallow, but I would imagine that lots of people will see &quot;C and Tcl&quot; and not look any further.&lt;/blockquote&gt;

to which, I responded:

&lt;blockquote&gt;That&#039;s the funny thing: the scalability and elegance of AOLserver comes from its use of C and Tcl.  You can compile and run PHP under AOLserver now, or use Tomcat for Java/JSP with AOLserver today, but then you&#039;re only using AOLserver as a HTTP request processor/proxy which doesn&#039;t get you very much benefit.

I&#039;ve always said that &quot;most websites are small, and for small websites, you can use just about ANY solution.&quot;  So, people build their small sites using their favorite technology (Apache with mod_perl, or PHP, or Java) and start becoming successful.  They quickly try to scale up their sites, and quickly hit the first wall: poor design.  Yes, most sites&#039; scalability problems are one of poor design, not a limiting factor of the technology.  This is the abysmal &quot;slowness&quot; that plagues most small sites.

However, there&#039;s a whole separate class of scalability problems that plague the larger sites.  It&#039;s the actual limiting factor of the underlying technology.  I imagine that very few sites ever hit this wall, because with low-cost commodity Intel hardware and ever-increasing CPU speeds, even the lamest dog can still hunt, today.  But, this limit can still be reached.  And, without real scientific evidence (i.e., this is purely anecdotal), I suggest that other web technology platforms reach this limit far sooner than AOLserver does.

But, recalling the more common cause of scalability problems (poor design which plagues all platforms), it&#039;s still not important today for most web development shops to care about their technology choices, but rather the people working with/for them.  But, I&#039;d still prefer to hedge my bets and build my applications on top of AOLserver regardless, so that when the day finally comes, I&#039;ll be able to continue to scale it when others can&#039;t.&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Joe Grossberg commented in <a href="http://www.livejournal.com/users/dossy/5666.html">my LiveJournal</a>:</p>
<blockquote><p>Wow, someone&#8217;s still using Tcl &#8230; having dabbled in Expect and Tcl/Tk &#8230; I can say that the support for other languages is key to growing its user and developer bases. I know it&#8217;s shallow, but I would imagine that lots of people will see &#8220;C and Tcl&#8221; and not look any further.</p></blockquote>
<p>to which, I responded:</p>
<blockquote><p>That&#8217;s the funny thing: the scalability and elegance of AOLserver comes from its use of C and Tcl.  You can compile and run PHP under AOLserver now, or use Tomcat for Java/JSP with AOLserver today, but then you&#8217;re only using AOLserver as a HTTP request processor/proxy which doesn&#8217;t get you very much benefit.</p>
<p>I&#8217;ve always said that &#8220;most websites are small, and for small websites, you can use just about ANY solution.&#8221;  So, people build their small sites using their favorite technology (Apache with mod_perl, or PHP, or Java) and start becoming successful.  They quickly try to scale up their sites, and quickly hit the first wall: poor design.  Yes, most sites&#8217; scalability problems are one of poor design, not a limiting factor of the technology.  This is the abysmal &#8220;slowness&#8221; that plagues most small sites.</p>
<p>However, there&#8217;s a whole separate class of scalability problems that plague the larger sites.  It&#8217;s the actual limiting factor of the underlying technology.  I imagine that very few sites ever hit this wall, because with low-cost commodity Intel hardware and ever-increasing CPU speeds, even the lamest dog can still hunt, today.  But, this limit can still be reached.  And, without real scientific evidence (i.e., this is purely anecdotal), I suggest that other web technology platforms reach this limit far sooner than AOLserver does.</p>
<p>But, recalling the more common cause of scalability problems (poor design which plagues all platforms), it&#8217;s still not important today for most web development shops to care about their technology choices, but rather the people working with/for them.  But, I&#8217;d still prefer to hedge my bets and build my applications on top of AOLserver regardless, so that when the day finally comes, I&#8217;ll be able to continue to scale it when others can&#8217;t.</p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using apc
Database Caching using apc
Object Caching 232/232 objects using apc

Served from: dossy.org @ 2012-05-21 01:58:25 -->
