S
showme
PHP and ASP.NET Go Head-to-Head
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html
SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.
So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>
comments?
By Sean Hull
http://otn.oracle.com/pub/articles/hull_asp.html
SUMMARY at the BOTTOM
Speed and efficiency. As I mentioned earlier, ASP.NET is a framework
allowing you to use various programming languages. In addition, it is touted
as having a great object-oriented model. All this is true, but it becomes a
detriment as far as speed is concerned. For all that advantage, there is a
lot more code to run through to execute the same ASP page than you have to
execute in the PHP engine for an equivalent PHP page. PHP is the
quick-and-dirty type of solution, the one to get the job done. And though a
lot of robustness has been added to it since its 2.0 and 3.0 days, it still
retains that core optimized high-speed approach.
Speed is not the only consideration. Memory usage is also important.
SECURITY COMPARISON
ASP.NET officially requires that you use IIS. Unfortunately, IIS has a long
history of vulnerabilities, which makes many administrators reluctant to
deploy it to handle their web site. Whether these weaknesses are because of
Microsoft's ineptness or because IIS is a real red flag to hackers is
irrelevant: Those systems have a history of being hacked and compromised.
PHP runs on Apache, too, which is fast and open source and has a good
security track record. Also, as I mentioned, Apache runs on many platforms.
So is PHP really faster than ASP.NET or is that for certain unoptimized
pages? And are they comparing this against the DataGrid instead of the
repeater control or even the fastest way using asp.net's inline code render
block, <% %>
comments?