Tony Cowderoy <[EMAIL PROTECTED]> > Matthew Pearson wrote: > > [...] What is it about PHP that you > > wouldn't consider it Enterprise class (especially when you consider the > > , rather large, wikis that run on it)?
Personally, I'd say PHP's biggest problem is the absolute rubbish that some PHP programmers produce. It is possible to write good PHP code, but it's often not as easy as spewing spaghetti-style. That's hardly the only language suffering from this, though. > PHP and Perl don't scale up (i.e. to one very big server) as well as > Java does, because the popular Java-based servers and JVMs have been > very carefully optimised to scale up well. [...] Over-generalise much? I've found JVMs to be scalable, but pretty fussy about their tuning. Far more so than normal PHP or Perl webservers. In fact, Java-based servers are enough trouble that I try to avoid them. > IMHO, the biggest reasons for using Java in practice are: > 1) fashion - [...] A bad and fairly irritating reason! > 6) at the risk of starting a flame war, Java's OOP and modularisation > facilities are, arguably, much more rigorous than Perl or PHP. [...] I'm not that familiar with PHP OO either, but it's probably true for Java compared with Perl 5. Java is not totally clean OOP, though: there are some frustratingly non-OO parts of the language, like the int/Integer dichotomy. Now, where's that spoof ORA "Java makes me want to smoke crack" cover that I used to have...? -- MJ Ray - personal email, see http://mjr.towers.org.uk/email.html Work: http://www.ttllp.co.uk/ irc.oftc.net/slef Jabber/SIP ask _______________________________________________ Peterboro mailing list [email protected] http://mailman.lug.org.uk/mailman/listinfo/peterboro
