<?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: Sites still in Classic ASP, why?</title>
	<atom:link href="http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/</link>
	<description>Kaweb</description>
	<lastBuildDate>Tue, 20 Jul 2010 07:13:48 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kai Semple</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-489</link>
		<dc:creator>Kai Semple</dc:creator>
		<pubDate>Fri, 11 Jun 2010 03:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-489</guid>
		<description>I came across this web site through Bing trying to find some great affiliate marketing guidance. This blog has that, appreciate it!</description>
		<content:encoded><![CDATA[<p>I came across this web site through Bing trying to find some great affiliate marketing guidance. This blog has that, appreciate it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tenorio</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-277</link>
		<dc:creator>Tenorio</dc:creator>
		<pubDate>Tue, 29 Dec 2009 03:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-277</guid>
		<description>Classic ASP still rocks, but you have to use the basic OO VBScript offers to avoid those horrible spaghetti-code.

Check it out Ajaxed library for classic ASP: www.ajaxed.org

Using ajaxed you can build modern ajax-like apps easily.

Long live classic ASP!</description>
		<content:encoded><![CDATA[<p>Classic ASP still rocks, but you have to use the basic OO VBScript offers to avoid those horrible spaghetti-code.</p>
<p>Check it out Ajaxed library for classic ASP: <a href="http://www.ajaxed.org" rel="nofollow">http://www.ajaxed.org</a></p>
<p>Using ajaxed you can build modern ajax-like apps easily.</p>
<p>Long live classic ASP!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ewan Stevenson</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-169</link>
		<dc:creator>Ewan Stevenson</dc:creator>
		<pubDate>Tue, 22 Sep 2009 09:04:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-169</guid>
		<description>I agree with what Robert Greene says - mix ASP and ASP.NET to suit requirements and you&#039;ve got something that really wins over PHP.</description>
		<content:encoded><![CDATA[<p>I agree with what Robert Greene says &#8211; mix ASP and ASP.NET to suit requirements and you&#8217;ve got something that really wins over PHP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Osuna</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-130</link>
		<dc:creator>Carlos Osuna</dc:creator>
		<pubDate>Mon, 20 Jul 2009 22:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-130</guid>
		<description>Why do people still code in Classic ASP?
Using Socratic thinking one would reply: Why do people still use COBOL?.

The real reason for classic ASP dominance in the market (I think in the enterprise market there is 5 classic apps for every PHP or ASP.NET stuff, only Java stacks in the numbers) is that it worked.

Microsoft tried to imitate Java with its ASP.NET but created a convulted Mom-and-Pop solution which doesn&#039;t scale.  PHP, in the other end, is a good scalable solution, but it&#039;s mostly ignored by the Enterprise, since it is not properly structured and recreates what companies are trying to avoid, scaling back from classicASP.  It has a great ecosystem, but most of its offerings are in the open source, end-user market.

So just like MFC, Visual Basic and Visual Fox are Windows client side legacy, classic ASP, COM+ and ADO are server side legacy platforms that will remain in existence from here to eternity.</description>
		<content:encoded><![CDATA[<p>Why do people still code in Classic ASP?<br />
Using Socratic thinking one would reply: Why do people still use COBOL?.</p>
<p>The real reason for classic ASP dominance in the market (I think in the enterprise market there is 5 classic apps for every PHP or ASP.NET stuff, only Java stacks in the numbers) is that it worked.</p>
<p>Microsoft tried to imitate Java with its ASP.NET but created a convulted Mom-and-Pop solution which doesn&#8217;t scale.  PHP, in the other end, is a good scalable solution, but it&#8217;s mostly ignored by the Enterprise, since it is not properly structured and recreates what companies are trying to avoid, scaling back from classicASP.  It has a great ecosystem, but most of its offerings are in the open source, end-user market.</p>
<p>So just like MFC, Visual Basic and Visual Fox are Windows client side legacy, classic ASP, COM+ and ADO are server side legacy platforms that will remain in existence from here to eternity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-85</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Tue, 28 Apr 2009 20:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-85</guid>
		<description>Hi

I worked on the CW Homes site when OrangeVision were running it back in 2003. 

I do agree that Classic ASP has had its day and should have been laid to rest years ago, the joys of legacy code. PHP is streets ahead of classic I agree.

I dont think its fair to say that asp.net and c# are a weaker product than PHP though, especially now that Microsoft have introduced MVC framework and integrated JQuery into the framework, weve just built a large application using this and I would really recommend it, well worth a look.

Kind regards
Stephen</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>I worked on the CW Homes site when OrangeVision were running it back in 2003. </p>
<p>I do agree that Classic ASP has had its day and should have been laid to rest years ago, the joys of legacy code. PHP is streets ahead of classic I agree.</p>
<p>I dont think its fair to say that asp.net and c# are a weaker product than PHP though, especially now that Microsoft have introduced MVC framework and integrated JQuery into the framework, weve just built a large application using this and I would really recommend it, well worth a look.</p>
<p>Kind regards<br />
Stephen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Greene</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-82</link>
		<dc:creator>Robert Greene</dc:creator>
		<pubDate>Fri, 17 Apr 2009 09:29:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-82</guid>
		<description>Great comment... Just one problem with it. You can integrate Classic ASP with ASP.NET and SilverLite which blows PHP out of the water by about 20 years!!

Also I can code full functions in ASP in just a few lines compared to PHP which would be a matter 50 - 60 lines just in simple functions alone. Compare 50-60 lines in ASP I can have almost a full program thats including the GUI!!</description>
		<content:encoded><![CDATA[<p>Great comment&#8230; Just one problem with it. You can integrate Classic ASP with ASP.NET and SilverLite which blows PHP out of the water by about 20 years!!</p>
<p>Also I can code full functions in ASP in just a few lines compared to PHP which would be a matter 50 &#8211; 60 lines just in simple functions alone. Compare 50-60 lines in ASP I can have almost a full program thats including the GUI!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: infocyde</title>
		<link>http://www.kaweb.co.uk/blog/why-are-websites-built-in-classic-asp/comment-page-1/#comment-80</link>
		<dc:creator>infocyde</dc:creator>
		<pubDate>Wed, 01 Apr 2009 18:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaweb.co.uk/?p=89#comment-80</guid>
		<description>I agree.  I coded a lot in classic ASP, and I have to admit I like it a lot.  When I coded in Classic ASP I found myself more focused on dealing with customer problems then figuring out how to do something techwise.  That is why I still think developers who have coded in ASP for a long time still turn out new sites written in ASP even though it is ten years old.  Now that I develop in ASP.Net/C#, I&#039;ve got all this power at my finger tips, but I&#039;m constantly getting tripped up on the technology rather then turning out something.  True, the problems I deal with now are more complex then when I did back when I was a classic ASP developer, but sometimes just having a few tools but knowing how to use them really well is better then having hundreds of classics and methods that seem to trip over themselves.

So for small data driven apps, ASP would be find IF it weren&#039;t for the fact that its future is uncertain.  Thus we have PHP.  I&#039;ve read about it and it look really similar to classic ASP as far as being simple but powerful, but it also looks like PHP can be extended quite a bit with modules and frameworks, so you can approach the power of .Net if you wanted to, or you can keep it simple by using just the base PHP features that you want to use.

That is pretty appealing.  As sometimes ASP.Net pisses me off, where simple scripting languages like ASP and PHP get the job done for 90% of what you want to do.

So, due to the fact that classic ASP might be going the way of the do do, I will work with PHP going forward for all my side gigs.</description>
		<content:encoded><![CDATA[<p>I agree.  I coded a lot in classic ASP, and I have to admit I like it a lot.  When I coded in Classic ASP I found myself more focused on dealing with customer problems then figuring out how to do something techwise.  That is why I still think developers who have coded in ASP for a long time still turn out new sites written in ASP even though it is ten years old.  Now that I develop in ASP.Net/C#, I&#8217;ve got all this power at my finger tips, but I&#8217;m constantly getting tripped up on the technology rather then turning out something.  True, the problems I deal with now are more complex then when I did back when I was a classic ASP developer, but sometimes just having a few tools but knowing how to use them really well is better then having hundreds of classics and methods that seem to trip over themselves.</p>
<p>So for small data driven apps, ASP would be find IF it weren&#8217;t for the fact that its future is uncertain.  Thus we have PHP.  I&#8217;ve read about it and it look really similar to classic ASP as far as being simple but powerful, but it also looks like PHP can be extended quite a bit with modules and frameworks, so you can approach the power of .Net if you wanted to, or you can keep it simple by using just the base PHP features that you want to use.</p>
<p>That is pretty appealing.  As sometimes ASP.Net pisses me off, where simple scripting languages like ASP and PHP get the job done for 90% of what you want to do.</p>
<p>So, due to the fact that classic ASP might be going the way of the do do, I will work with PHP going forward for all my side gigs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
