From: Rasputin Date: 2003-05-07T23:11:30+09:00 Subject: Re: Why is PHP so popular? What can we learn from the PHP camp? * Brian Candler [030506 11:34]: > On Tue, May 06, 2003 at 04:52:56AM +0900, E F van de Laar wrote: > > Just wanted to mention that in all the replies so far no one has > > mentioned Java. Applications servers built on J2EE and running Servlets > > are on the rise and fast. > > I would disagree there - I have never seen *any* Java application which is > fast! :-P > Actually, all the Java apps I've seen have not only been slow but also buggy > as hell when put under load ('under load' sometimes means three > keystrokes) which gives me a rather negative impression overall. Client side Java - particularly GUI code - is absolutely awful. 'Write once, debug everywhere'. Life's too short. Server-side, it's a different story. The servlet API is a joy to use, and speedwise it p*sses all over CGI. - being able to initialise your DB connection when the server boots then re-use it is a real boon. The rest of J2EE (EJB in particular) always seemed like overkill, but then I don't run legacy databases.... IMO, ruby appservers are the way to go, rather than a CGI-based approach have persistent objects on the server, and spawn a new thread for each client. The servlet model is A Good Thing for OOP code, as opposed to a 'when the client connects fork off a shell with this in' legacy approach. Add a well defined interface to the container that your Ruby servlets (Garnets?) run in, so you can get the same sort of portablility across appservers Java gives you. Once I know enough, I'll be back here asking dumb questions to see what I can do to make that happen. > Oh, and it's an encumbered technology - I had to agree to terms and > conditions before downloading it. For us up at the ISP, that's not a new thing. But at least I can choose tomcat over weblogic and pocket the difference if I want, without a lot of porting hassles. -- Rasputin :: Jack of All Trades - Master of Nuns