Re: PHP and ASP.NET go HEAD to HEAD

From: Kevin Spencer (kspencer_at_takempis.com)
Date: 07/08/04 

Date: Thu, 8 Jul 2004 09:52:05 -0400

> comments?

Consider the source. Also note that a number of comparison criteria are
simply ignored, such as development speed/cost. The most expensive aspect of
development is the cost of developers (man-hours of dev time). While ASP.Net
consumes a large chunk of memory and processor, RAM is cheap; hardware is
cheap; programmers are expensive. ASP.Net is designed to give the
implementers a greater ROI. This is the bottom line when it comes to
software development. That is why Oracle is in so much trouble financially.
It costs more to use it. 

-- 
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"showme" <showme@hotmail.com> wrote in message
news:#A4l#xNZEHA.3692@TK2MSFTNGP09.phx.gbl...
> 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?
>
>
>
>
>

Relevant Pages

  • Re: Apache vs IIS
    ... Windows Server not on my Linux Server so there for I would chose IIS. ... Not that Apache is bad but ASP.NET is far easier and faster to create good web forms in. ... PHP on a IIS server is rather easy to run once you install PHP on a PC but if you only use PHP why not use Apache for Windows. ...
    (alt.php)
  • Re: Apache vs IIS
    ... my Windows Server not on my Linux Server so there for I would ... IIS is designed for ASP, ... can run asp on Apache, ... in running php from IIS vs Apache. ...
    (alt.php)
  • Re: PHP + IIS + Visual Studio.NET 2005 and Apache
    ... The apache version that comes with VS.Php however will shut itself down ... Apache or IIS. ... to use the DBG module installed inside PHP inside the version of Apache ... bundled with VS.php in case you do not have any other web server installed. ...
    (alt.php)
  • Re: Apache vs IIS
    ... my Windows Server not on my Linux Server so there for I would chose IIS. ... Not that Apache is bad but ASP.NET is far easier and faster to create good web forms in. ... IIS is designed for ASP, ... PHP on a IIS server is rather easy to run once you install PHP on a PC but if you only use PHP why not use Apache for Windows. ...
    (alt.php)
  • Re: PHP and ASP.NET go HEAD to HEAD
    ... > execute in the PHP engine for an equivalent PHP page. ... > ASP.NET officially requires that you use IIS. ... Those systems have a history of being hacked and compromised. ... Also, as I mentioned, Apache runs on many ...
    (microsoft.public.dotnet.framework)
Loading