PHP vs. Java

[lawrence]

Re: PHP vs. Java

Drazen Gemic <dgemic@nospam. net> wrote in message news:<pan.2003. 07.10.15.56.30. 864301.770@nosp am.net>...[color=blue]
> Java great measure of isolation from the operating system is the
> advantage on microsoft operating systems, where unwanted suprises are
> always likely to happen.[/color]

To summarize, then:

Small-Medium Sites: PHP is good.

Big Sites: Java is good.

[André Næss]

Re: PHP vs. Java

lawrence:
[color=blue]
> Drazen Gemic <dgemic@nospam. net> wrote in message
> news:<pan.2003. 07.10.15.56.30. 864301.770@nosp am.net>...[color=green]
>> Java great measure of isolation from the operating system is the
>> advantage on microsoft operating systems, where unwanted suprises are
>> always likely to happen.[/color]
>
> To summarize, then:
>
> Small-Medium Sites: PHP is good.
>
> Big Sites: Java is good.[/color]

Define Small-Medium and Big. Do you mean in terms of traffic? Complexity?
Functionality?

André Næss

[Metnetsky]

Re: PHP vs. Java

On Wed, 09 Jul 2003 10:07:50 -0400, Bruce Lewis wrote:
[color=blue]
> "Metnetsky" <mimetnet@syr.e du> writes:
>[color=green]
>> Not to start a flame-fest, but no database is smart enough to handle
>> half of the business logic that any medium size website has.[/color]
>
> I guess the easy way to avoid a flame fest would be to post an example
> of business logic that cannot be handled by a database. That would shut
> up all the flamers, wouldn't it?
>
> Go ahead. I'm waiting.[/color]

You can very well put a lot of your core logic into stored procedures in a
relational database, but more advanced logic such as recursive functions
and what not would be much more complex to develop in procedural SQL.
Moreover, if you have your back-end logic compiled [java, c] would be
faster than a database. Also using your logic in code instead of the db
would make your life easier with various interfaces such as soap, flash,
etc. as well as a better error handling.

[lawrence]

Re: PHP vs. Java

André Næss <andrena.spamre allysucks@ifi.u io.no> wrote in message news:<bekbt8$ov n$1@maud.ifi.ui o.no>...[color=blue]
> lawrence:
>[color=green]
> > Drazen Gemic <dgemic@nospam. net> wrote in message
> > news:<pan.2003. 07.10.15.56.30. 864301.770@nosp am.net>...[color=darkred]
> >> Java great measure of isolation from the operating system is the
> >> advantage on microsoft operating systems, where unwanted suprises are
> >> always likely to happen.[/color]
> >
> > To summarize, then:
> >
> > Small-Medium Sites: PHP is good.
> >
> > Big Sites: Java is good.[/color]
>
> Define Small-Medium and Big. Do you mean in terms of traffic? Complexity?
> Functionality?[/color]

What difference do you mean to highlight by asking first about
complexity and then about funtionality? What is the difference that
you see?

[André Næss]

Re: PHP vs. Java

lawrence:
[color=blue][color=green][color=darkred]
>> > To summarize, then:
>> >
>> > Small-Medium Sites: PHP is good.
>> >
>> > Big Sites: Java is good.[/color]
>>
>> Define Small-Medium and Big. Do you mean in terms of traffic? Complexity?
>> Functionality?[/color]
>
> What difference do you mean to highlight by asking first about
> complexity and then about funtionality? What is the difference that
> you see?[/color]

Complexity: Very complex operations need to be performed to serve requests,
e.g. doing huge calculations on each request (for whatever purpose).

Functionality: Lots of functionality :) Basically the number of things users
can do, each task may be simple or complex to actually implement. Making
them all interact an work together can be hard.

And I would also like to add another axis: Large/small datasets. Is the site
big or small in terms of the data it supplies? For example a site that
offers basic queries towards a database of all known movies has a large set
of data but doesn't have to be neither complex nor rich in functionality.

All these obviously overlap, but different sites will have different
profiles. My main point was of course that your very simple rule is in fact
far too simple.

André Næss

[lawrence]

Re: PHP vs. Java

André Næss <andrena.spamre allysucks@ifi.u io.no> wrote in message[color=blue]
> Complexity: Very complex operations need to be performed to serve requests,
> e.g. doing huge calculations on each request (for whatever purpose).
>
> Functionality: Lots of functionality :) Basically the number of things users
> can do, each task may be simple or complex to actually implement. Making
> them all interact an work together can be hard.
>
> And I would also like to add another axis: Large/small datasets. Is the site
> big or small in terms of the data it supplies? For example a site that
> offers basic queries towards a database of all known movies has a large set
> of data but doesn't have to be neither complex nor rich in functionality.[/color]


Then, obviously, the answer is complexity.