Women in Technology

Article:		The PHP Scalability Myth
Subject:		Java on a server
Date:		2003-10-17 10:00:53
From:		anonymous2
Just like to point out that Java, on a server, isn't interpreted code. It's dynamically profiled and compiled code. Which should yield much better performance and memory utilization then either interpreted or just compiled code. At a cost of a larger minimum memory size to implement. Sun recommends a minimum of 2G of Ram.

Showing messages 1 through 2 of 2.

• Java on a server
  2003-10-19 11:27:22  anonymous2 [View]
  
  
  What? You seriously think Java is faster than compiled code? OK, you solve a problem in Java, and I'll solve it in C.
  
  Java might be comparable to PHP, but I don't see it ever competing with C in terms of performance alone. That isn't what it was designed for.
• Java on a server
  2003-10-29 12:40:21  anonymous2 [View]
  
  
  Apart from Java being slower to develop in (so the greedy little pickpockets can get fatter consultant checks), I don't see any reasons for anyone to write anything in Java.
  C code can be written just as portable as Java, and if properly done it will run with less CPU overhead and with considerably less memory.
  As a comparison, Linux (which is written in C with a few required steps of assembly code) runs just fine on an SX33 with 8Mb of RAM. Try that with a java applet of choice. Or maybe you shouldn't. After all, 8Mb <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 2Gb.