Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For me this comes down to performance. When you look at PHP it has certainly been deployed on extremely large platforms (Facebook used it almost exclusively at the beginning), but in general it is used on smaller platforms. Java, for me, when you look at it's scalability benefits is superior, but only when you know you're going to be scaling. </p> <p>Understanding the underlying life cycle of a request is very important. That is, knowing what a Java container is and how a Tomcat server runs helped me understand tremendously the performance implications.</p> <p>Don't try to choose one over the other over single attributes such as "ease of coding" or "database connectivity"- they are different enough that by focusing on just a couple of "important" things you'll be essentially selecting based off of biased information. That is, PHP makes it easier to connect to a DB if you look at them on a surface level- "Ugh! I have to install a JDBC, wtf is that???", etc- but that's the lazy man's excuse. There is nothing Java can't do that PHP can (that I'm aware of). </p> <p>For me the question is how do you <strong><em>realistically</em></strong> (<strong>Read: realistically</strong>) see your application working- do you plan on getting thousands of visits per hour or are you talking a hundred hits a day like the grand majority of the little projects out there?</p> <p>The benefits of PHP on smaller projects, particularly for the programmer that doesn't fully grasp OOP architecture are enormous- but don't get lazy and just take PHP because it's easier out of the box. Java is extremely powerful and simply by learning it can teach you more than you realized you didn't know about OOP and good programming practices in general (if you come from the self-taught realm like I do).</p> <p>Basically, I'd say analyze your estimated project load plus ramp-up time if you have to learn one or the other, gauge your efficiency and scalability requirements, keep asking questions, and then decide which platform is better. </p> <p>Hope that helps....!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload