Linux and Solaris users tend to be very concerned with performance more then Windows users. To be honest I think the biggest reason Java hasn't found a home in Linux was the lack of a quality JDK. For the longest time JDK support under linux was way behind the quality and speed of its implemenation. That's sun fault.
Sun was never interested in java until IBM got involved, and make no mistake about it, IBM is far more important to java then Sun. IBM spends twice as much Sun on java development. Of the 33,000 tests in the Sun Java Compability Test Kit (JCK), 22,000 of those were developed by IBM. IBM's investment in java is simply huge, and given their new linux direction and focus, I full expect full java ports of WebSphere to help java find a place on the smaller linux platforms.
Java's place in this world is the Enterprise server level, not embedded servers as the author of the article laughably suggests. Enterprise means big hardware, and big money, and quite frankly linux's Intel ties are part of the problem. Quad or eight way xeon machines just don't offer as much as the solaris or hp-ux big server racks. That may not seem important to the average slashdot user, but it is critcal to SprintPCS running SilkNet on 50 WebLogic installs or to Charles Schwab running the 40 installs of WebSphere on IBM hardware.
These are the companies that are driving java development, and they're not real interested in 'toy' Intel deployments. Intel knows this all to well, and has developed the Itanium chip in response. It should be interesting.
Now, as for java performance, its pretty easy to write a slow java app, I'm talking server side, as most java apps use HTML/JSP for their client side interaction. Its difficult to profile a java application, so tweaking it after the fact is very not smart. You MUST keep in mind performance as you create the java application. Garbage collection, exception handling, and database I/O are all major java chokepoints.
As app server vendors start search for new markets (with the big customers having bought their server licenses already), linux will be a more important focus for these vendors, and java will start to play a larger role in their product plans.
"Try win2000 and have it work right the first time!"
Horse Hockey.
I'll remember this the next time the 3com nics in my office loose track of the DNS Server they've been told to look at via DHCP, and start resolving things with an external IP address.
Annoying.... wouldn't mind looking in the drive source to see what is causing that.
Slashdot Mirror
Linux and Solaris users tend to be very concerned with performance more then Windows users. To be honest I think the biggest reason Java hasn't found a home in Linux was the lack of a quality JDK. For the longest time JDK support under linux was way behind the quality and speed of its implemenation. That's sun fault.
Sun was never interested in java until IBM got involved, and make no mistake about it, IBM is far more important to java then Sun. IBM spends twice as much Sun on java development. Of the 33,000 tests in the Sun Java Compability Test Kit (JCK), 22,000 of those were developed by IBM. IBM's investment in java is simply huge, and given their new linux direction and focus, I full expect full java ports of WebSphere to help java find a place on the smaller linux platforms.
Java's place in this world is the Enterprise server level, not embedded servers as the author of the article laughably suggests. Enterprise means big hardware, and big money, and quite frankly linux's Intel ties are part of the problem. Quad or eight way xeon machines just don't offer as much as the solaris or hp-ux big server racks. That may not seem important to the average slashdot user, but it is critcal to SprintPCS running SilkNet on 50 WebLogic installs or to Charles Schwab running the 40 installs of WebSphere on IBM hardware.
These are the companies that are driving java development, and they're not real interested in 'toy' Intel deployments. Intel knows this all to well, and has developed the Itanium chip in response. It should be interesting.
Now, as for java performance, its pretty easy to write a slow java app, I'm talking server side, as most java apps use HTML/JSP for their client side interaction. Its difficult to profile a java application, so tweaking it after the fact is very not smart. You MUST keep in mind performance as you create the java application. Garbage collection, exception handling, and database I/O are all major java chokepoints.
As app server vendors start search for new markets (with the big customers having bought their server licenses already), linux will be a more important focus for these vendors, and java will start to play a larger role in their product plans.
EvilJohn
... and should scale to the level of the user.
The idea that interfaces should be a one-size- fits-all implmenation is what needs fixing.
"Try win2000 and have it work right the first time!"
Horse Hockey.
I'll remember this the next time the 3com nics in my office loose track of the DNS Server they've been told to look at via DHCP, and start resolving things with an external IP address.
Annoying.... wouldn't mind looking in the drive source to see what is causing that.