On 26 Apr, 15:43, firewoodtim <firewood...@cavtel.netwrote:
Why limit this discussion to PHP vs Java? I program in PHP, but I
have been looking around for a different language to add to my bag of
skills, and a professor at a local college, who has experience in both
PHP and Java,tells me he is sold on .NET. He likes both C# and VB.
The problems he found with Java, he says, are "just fixed" in .NET.
Now what do you think of that?
On Sat, 26 Apr 2008 00:00:02 -0700 (PDT), tenxian
<hi.steven...@gmail.comwrote:
Is PHP more suitable for developing an interactive website than Java/
J2EE?
The problems with Java are now well-discussed in the open - so it
would be fairly easy for anyone to come along and write a better
version of the language - unfortunately Sun were encumbered with a
legacy they couldn't really walk away from.
But .NET introduces a whole set of problems on its own - Microsoft
don't really produce programming languages - they produce products.
What you can do with these products is severely constrained -
similarly what other people can help you with is also limited e.g.
http://www.regdeveloper.co.uk/2007/0...t_mvp_threats/ It
remains a single vendor product tied into that vendors other products.
In a number of areas Microsoft have profited from controlling access
to the product but also to information about the product; training is
now a major revenue stream for the company. They have also profited
from making their systems incompatible with those from other vendors
(witness SSL keep-alives). Endorsing this approach enforces a monopoly
position which has been proven to be abused in the past.
Java exists in a very healthy eco-system being first to market with a
fairly flexible core language with little platform dependancy.
Despite the existence of GUI widget bindings for PHP its current
memory management model is highly unsuited to desktop applications
(and that IMHO is GOOD thing). Unfortunately people still perceive
universal applicability of a language is a good thing - when really
its something of a myth. The same memory management which makes Java
work well for standalone applications undermines its effectiveness as
a web development language. Why do you think groovy, jython et al.
exist?
Similarly because Java did not wish to be too dependant on an existing
way of solving a problem, it has frequently gone off and built
byzantine and obscure but brutally 'correct' ways of doing things -
like JMS and JNDI.
Piotr wrote:
Java as a language is far more mature and is better suited for big projects.
PHP still doesnt do best in very big projects (though it's improving),
It's certainly easier to establish good programmer credentials using
Java compared with PHP. Leaving aside the issue of certification, you
simply can't write a working J2EE application unless you're a
proficient Java programmer. But it requires significantly less skill
to write a working PHP application - unfortunately the differences
will show up in terms of scalability, security and maintainability -
which are more difficult to prove than simple functionality.
I have never found any evidence to substantiate the claim that PHP is
less effective for large scale projects. IMHO the difference is due to
the fact that PHP does not have as well developed an eco-system; the
lack of namespaces is probably the main issue, but rather than finding
ways to avoid the problem (like continious integration) a great deal
of time and effort has been spent in addressing it directly.
C.