Python/Perl/PHP versus Java

In terms of enterprise web development why would you choose Java over Python/Perl/PHP? I ask this question because i've done significant web development with both Python and PHP and have recently been dabbling with jboss/tomcat/j2ee and have found that Java is very cumbersome. Not only is it a pain to program for, it is a resource hog. My personal opinion is that Java is an unweildly language obfuscated by marketing/legal mumbo jumbo. Just trying to find/download anything from Sun's website requires an immense amount of patience. I've come to the conclusion that the only companies wanting to implement any web frontend/backend in Java have a huge burning hole in their pockets.

Sorry if this sounds like a rant, but I just want some honest responses.

My personal opinion is that Java is an unweildly language obfuscated by marketing/legal mumbo jumbo. Just trying to find/download anything from Sun's website requires an immense amount of patience. I've come to the conclusion that the only companies wanting to implement any web frontend/backend in Java have a huge burning hole in their pockets.

Well Sun's target for Java is the professional market, not hobbyists. Java is a resource hog - 1.5 isn't that bad, but 1.4 and 1.3 both had some issues. Where Java really shines for web programming is high volume sites. You should hear some of the nightmares of people running Apache and trying to serve a high amount of users with a Perl frontend. You'll hear about all sorts of hacks (mod_perl hacks and DBC modifications) , etc. to help ease all the simultaneous database connections that are going on. I've heard of similar nightmares with Python and PHP.

Also, most companies that do use Java for web frontends don't worry about the complexities of Struts, J2EE, etc. They have programmers that just worry about writing the frontend, and system administrators that implement the applications once they've been written. I'm sure you're finding it tedious to try to program with Java and maintain a J2EE configuration. That's not what any real environment will be like, though.

Python makes mutli-threading a piece of cake. Two interfaces are provided. The low level interface and the easy way is to basically do this:

start_new_thread(function_name, args)

You can't get any simpler than that.

The other interface is high level uses the thread class. You pass the target and various other parameters to the constructor. To start the thread you do threadname.start(). You can even daemonize a thread by using the setDaemon function.

------

As for distributed computing, just check out the original Bit torrent project. IBM also offers a good intro into grid computing with python:

If Yahoo isn't big enough I don't know what is. Also check out Sourceforge.

------

I haven't had an issues with the postgresql bindings. If it is an issue you can always create a c++ module that uses the c++ bindings that you import into your programs. But I guess thats what they do already anyway.

Also, most companies that do use Java for web frontends don't worry about the complexities of Struts, J2EE, etc. They have programmers that just worry about writing the frontend, and system administrators that implement the applications once they've been written. I'm sure you're finding it tedious to try to program with Java and maintain a J2EE configuration.

That's a major problem. You need more people maintaining and as a result costs a lot more money. I would prefer to throw more computers at the problem than pay full salaries.

That's a major problem. You need more people maintaining and as a result costs a lot more money. I would prefer to throw more computers at the problem than pay full salaries.

I agree. Almost any language can be made to work in a situation if you're willing to throw enough time and money at it. What does that tell you about the language? Almost nothing.

People are far too willing to forgive programmers and companies that produce overly complex products and then justify it after the fact by claiming that the tool is only "designed for professionals". There's a big difference between "designed for professionals" and "you need lots of time and money to burn in order to make this work". The second doesn't necessarily imply the first.

People are far too willing to forgive programmers and companies that produce overly complex products and then justify it after the fact by claiming that the tool is only "designed for professionals". There's a big difference between "designed for professionals" and "you need lots of time and money to burn in order to make this work". The second doesn't necessarily imply the first.

Somewhat; for things like J2EE (which actually was designed for large, heavyweight systems) I don't think it's wrong to tell someone that this tool wasn't designed for them. So long as it's done up front.

Somewhat; for things like J2EE (which actually was designed for large, heavyweight systems) I don't think it's wrong to tell someone that this tool wasn't designed for them. So long as it's done up front.

Well, if you disect the J2EE acronym you get Java 2 Enterprise Edition. This should tell you whether or not it's designed for you. I won't argue the fact that J2EE is a very complex product. You have Tomcat, ant (I believe, they're including this nowadays), and the whole administration interface, a few plugins for LDAP, Web Start (this allows rapid remote deployment of Java applications - very nice, too), plus J2SE.

so-crates, of course Java can be used to make online games, but I actually prefer flash games because the stupid JVM doesn't keep on crashing. Regardless, the focus of this thread is on server-side programming, not client-side.

Well, if you disect the J2EE acronym you get Java 2 Enterprise Edition. This should tell you whether or not it's designed for you. I won't argue the fact that J2EE is a very complex product. You have Tomcat, ant (I believe, they're including this nowadays), and the whole administration interface, a few plugins for LDAP, Web Start (this allows rapid remote deployment of Java applications - very nice, too), plus J2SE.

This is what I mean by marketing mumbo jumbo. If I forked Python and renamed it to Python Enterprise Edition, other than being a really bad acronym (PEE) :rofl: , does this make it any more appropriate for enterprise level programming?

Well, if you disect the J2EE acronym you get Java 2 Enterprise Edition. This should tell you whether or not it's designed for you. I won't argue the fact that J2EE is a very complex product. You have Tomcat, ant (I believe, they're including this nowadays), and the whole administration interface, a few plugins for LDAP, Web Start (this allows rapid remote deployment of Java applications - very nice, too), plus J2SE.

Just sticking "Enterprise Edition" into a name isn't being upfront. Sure, I know that some guy running a server out of his basement shouldn't use it, but how large should a company have to be before they have enough resources to get a J2EE-based system working?

I think the standard edition is unnecessarily complex, but it's still good enough to be useful. I just wish more of an effort was made to make the language good at doing simple things.

This is what I mean by marketing mumbo jumbo. If I forked Python and renamed it to Python Enterprise Edition, other than being a really bad acronym (PEE) :rofl: , does this make it any more appropriate for enterprise level programming?

If PEE did have a simple package that contained Python, bundled with Apache and some plugins, a sleek web administration interface to distribute the Python apps to multiple servers, I would consider that Enterprise. If you haven't gotten it by now, an "Enterprise" package is something that is easy to administer for a high volume of users. J2EE has a all of thus: a) the web administration interface makes it very, very easy to move Java apps/containers across systems b) for client-side apps, show me a utility that does something like Web Start c) there's plenty, plenty of API documentation.

Java could be streamlined a bit more. What people neglect to think of is that Java is a whole language. C has been around for much longer, and it's integration into an operating system is much cleaner. Sun, however, has to produce a version of Java for Linux, Solaris, and Windows, which is by no means an easy task. Each of those OSs are supported as well as the other ones (there are a few exceptions pertaining to file i/o and SWT). Sun also produces an Enterprise distribution for each of those respective platforms. Does Perl, PHP, or Python have a single package for Linux, Solaris, and Windows to install that configures Apache, comes with a slick web interface, and much more? No, you do it yourself, and that does not qualify it as enterprise-worthy.

Edit: Zend, a PHP server that is propiertary, is an exception to the above statement about Enterprise readiness.

Hmm, I found this page quite interesting. I'll have to d/l the latest versions of Java, Python and Perl and see if its true. Wouldn't look too good for Python if it is.

I think part of the reason for Java's success is it had a very easy to use, platform independent (OK, Unix and Windows) GUI long before Python or C++ ever did, and it people started using it for other things despite some of its deficiencies.