PHP vs ASP and JSP again.

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Tim Chung

    PHP vs ASP and JSP again.

    Hey all,

    I am just wondering why all people use PHP if ASP.NET and JSP
    can offer better performance in a system requires a lot of operation
    processing (in my own understanding, because .NET and Java business
    components classes are pre-compiled already).

    Thanks in advance.

    Regards,
    Tim Chung
  • Daniel Tryba

    #2
    Re: PHP vs ASP and JSP again.

    Tim Chung <timothychung@g mail.com> wrote:[color=blue]
    > I am just wondering why all people use PHP if ASP.NET and JSP
    > can offer better performance in a system requires a lot of operation
    > processing (in my own understanding, because .NET and Java business
    > components classes are pre-compiled already).[/color]

    You could find such discussions in the history of this (and various
    others) group. But short and simple (IMHO):
    -PHP the language is extremly simple
    -PHP the environment is wide spread
    -PHP is (more) multi platform.
    -ASP.net, Java/Servlets/JSP come with a VM overhead, which could be
    a huge impact on light weight machines.

    Comment

    • Jasper Bryant-Greene

      #3
      Re: PHP vs ASP and JSP again.

      Tim,

      Many people use PHP for many reasons. A lot of people prefer that PHP
      does not force OO upon the programmer, as OO is not suitable for all
      programs.

      The performance issue is an interesting one. In my own experience, PHP
      is the fastest of the three, but I have only tested with a very small
      set of scripts which are likely to be suited to PHP more than the
      others. OO programs do tend to be slower. As an aside, you can
      precompile your PHP scripts into bytecode so that the entire script
      doesn't need to be compiled at runtime.

      Rather than get into an in-depth discussion of this here, which is
      bound to start a flame war, I'm instead going to point you to some
      websites with more information on the topic:

      == PHP vs. ASP.NET ==
      web blazonry Learn web technologies PHP, MySQL, java, javascript, style sheets, server-side scripting including examples, tutorials, source code and recomended books and resources. Also home of wu-name, U.S. English name and baby name generators.

      http://www.oracle.com/technology/pub.../hull_asp.html and






      == PHP vs. JSP ==


      Build the skills your teams need. Give them the O'Reilly learning platform and equip them with the resources that drive business outcomes.





      Comment

      • thehuby

        #4
        Re: PHP vs ASP and JSP again.

        Because PHP is extremely easy to program (though I am a JSP developer
        not a .NET one) in comparison. It also has, far and away (IMHO) the
        best resources and open source material on the internet - someone has
        already done most of the hard work for you if you are any good at using
        Google :)

        Hosting is generally cheaper too- even premium/dedicated stuff.

        PHP is also better understood by the current generation of developers.

        I'm a JSP developer predominantly but have really come to appreciate
        PHP - things are so easy in it that for small scale apps it is a good
        choice. I also think that people overplay the performance issues - if
        you have a good dedicated server for PHP it is not going to be much
        different in speed than a JSP or .NET server.

        If you want to start looking at larger scale apps then I would suggest
        JSP/J2EE and .NET offer a better framework for developing, but not
        because of performance - having precomiled classes & webpages as well
        as strong typing mean that run time errors are much less likely to
        happen.

        Rick Huby


        Comment

        • Colin McKinnon

          #5
          Re: PHP vs ASP and JSP again.

          thehuby wrote:
          [color=blue]
          > Because PHP is extremely easy to program (though I am a JSP developer
          > not a .NET one) in comparison. It also has, far and away (IMHO) the
          > best resources and open source material on the internet - someone has
          > already done most of the hard work for you if you are any good at using
          > Google :)
          >[/color]
          <snip>[color=blue]
          >
          > I'm a JSP developer predominantly but have really come to appreciate
          > PHP - things are so easy in it that for small scale apps it is a good
          > choice. I also think that people overplay the performance issues - if
          > you have a good dedicated server for PHP it is not going to be much
          > different in speed than a JSP or .NET server.
          >[/color]

          Define scale.

          In terms of dealing with huge volumes of throughput, PHP scales much more
          easily across a cluster than JSP (no RMI overhead). It's just a matter of
          throwing more iron at the problem. If you're Google, then hardware cost
          will outweigh programmer time, but if you're Google you probably won't be
          using JSP/ASP either.
          [color=blue]
          > If you want to start looking at larger scale apps then I would suggest
          > JSP/J2EE and .NET offer a better framework for developing, but not
          > because of performance - having precomiled classes & webpages as well
          > as strong typing mean that run time errors are much less likely to
          > happen.
          >[/color]

          I think we had this debate already.

          C.

          Comment

          • Rob Tweed

            #6
            Re: PHP vs ASP and JSP again.

            You may want to check out our eXtc Web Developer product
            (www.mgateway.com/php/mgw/ewd.php). Though it's currently tied to the
            Cache database, the interesting thing about it is that it provides an
            abstracted web application development approach that is end-technology
            independent. So, from the Design Pages that define a web application,
            eXtc Web Developer compiles the application into either PHP or JSP
            (we're going to add ASP.net in the near future).

            You can then choose the right platform (PHP or JSP) for your
            application, or change downstream if/when the relative performance
            benefits of the different run-time technologies change. And you don't
            need cross-training in each technology or know or understand the
            intricacies of PHP or JSP.




            On Thu, 16 Jun 2005 09:13:46 GMT, Tim Chung <timothychung@g mail.com>
            wrote:
            [color=blue]
            >Hey all,
            >
            >I am just wondering why all people use PHP if ASP.NET and JSP
            >can offer better performance in a system requires a lot of operation
            >processing (in my own understanding, because .NET and Java business
            >components classes are pre-compiled already).
            >
            >Thanks in advance.
            >
            >Regards,
            >Tim Chung[/color]

            ---
            Rob Tweed
            M/Gateway Developments Ltd

            Global DOMination with eXtc : http://www.mgateway.tzo.com
            ---

            Comment

            • Centurion

              #7
              Re: PHP vs ASP and JSP again.

              Tim Chung wrote:
              [color=blue]
              > Hey all,
              >
              > I am just wondering why all people use PHP if ASP.NET and JSP
              > can offer better performance in a system requires a lot of operation
              > processing (in my own understanding, because .NET and Java business
              > components classes are pre-compiled already).[/color]

              I work for a company that builds big (I mean BIIIIG) web applications for
              transaction-based e-commerce business models. We are nearing completion of
              the transition from ASP.Net to JSP. The reasons are two fold:
              1. cross-platform support
              2. due to #1, the ability to better tailor the hardware and software (OS)
              for individual customer requirements.

              What we've found is that performance between the two offerings was very
              similar, but once we moved away from Windows+Intel[1] to Linux+AMD64 the
              real performance advantages started to be obvious.

              Java on 64bit platforms simply wins hands down in the bangs-per-buck stakes
              when pitted against Windows on IA32. I guess that's rather obvious, but we
              didn't expect to see performance gains in orders of magnitude for
              throughput and 70-80% improvements is script runtime etc.

              [1] Xeon 3GHz class machines - not toy P4's etc.

              James
              --
              I hate small towns because once you've seen the cannon in the park
              there's nothing else to do.
              -- Lenny Bruce

              Comment

              Working...