It depends, actually. If you're already running another Java app, the startup is quicker.
JUST LIKE a KDE app starting up in KDE, or a GTK app starting in Gnome. Obviously graphic libraries have to be loaded. What I was referring to is runtime responsiveness.
And I was not referring to networking at all. Java is a threaded environment, something not truly supported by the 2.4 linux kernel. I was referring to the necessary hack in place to work Java in a non-threaded OS.
The only thing Java is still "slow as hell" with is GUI on Linux. I've run plenty of tests vs C++, Obj-C, Perl, Python, etc. on non-GUI implementations of the same spec (proprietary in-house infrastructure spec).
GUI on Linux is slow for one reason: the linux implementations of Java pre-2.6 linux kernel has avoided the POSIX threading (because it had to) and used processes communicating through shared memory instead of operating from the same address space. This is most significant for GUI apps because in Java each Listener runs in its own Thread.
IF Sun releases a true thread-using implementation for linux you'll see a BIG performance gain on the GUI and maybe some gain elsewhere as well, but in the meantime I have to request (again) that folks not dump on Java unless they've used it within the previous year.
Microsoft has a very long future developing games. For linux.:)
Seriously, what other software could be sold when so many people are developing free alternatives? Games are the last proprietary software the world will ever see (since the primary component is in the design and not the actual code). It's more like art than software in that respect.
So welcome, Microsoft, to your niche. You'll find that the next generation of X-server that supports sound and openGL a joy to work with.
The biggest reason that Java is a resource hog on Linux is that it's current implementation is a hack. Using shared memory segments to communicate between process threads is not how the runtime was intended to be implemented. Now that 2.6 has *real* threading, we'll see what Java can do in Linux with green threads. I think many people will be surprised. (I've personally surprised a few Java bigots where I work by outpacing their C++ and Objective-C code with Java solving the same problems, but that's a single-threaded server process with no GUI.) IMHO, Java is the right direction, and gcj is my greatest hope.
One comment: for a company of IBM's size, two years is a VERY short time to switch every desktop to a different OS. I work for a much smaller company and our estimates are that a switch like that would have to happen in a phased implementation over AT LEAST two years.
Unfortunately 98% of people vote for whomever's message was repeated the most times while they enjoy their post-dinner coma in front of the television each night.
So I predict that the winner will be the biggest spender on television advertising. Internet usage typically requires thought (and, oh my! READING), so it's much less effective.
Psion has never actively pursued the consumer market; they consider the enterprise to be their niche. In some ways, the device is more rugged than other alternatives, and with no HD you do have increased battery life without an extra extension battery.
The new model also boasts the ability to store things you don't want to lose in a total power failure on an internal flash card (which is nice in comparison to the original netBook that had no internal persistent storage).
I don't at all prefer CE.Net, and would have liked to see them at least offer a port of Linux, but I guess there's business decisions that overrule technical ones.
Slashdot Mirror
You can download a better OS for free.
Ok, ok. So whenever you need a single dialog, don't use Java.
It depends, actually. If you're already running another Java app, the startup is quicker.
JUST LIKE a KDE app starting up in KDE, or a GTK app starting in Gnome. Obviously graphic libraries have to be loaded. What I was referring to is runtime responsiveness.
And I was not referring to networking at all. Java is a threaded environment, something not truly supported by the 2.4 linux kernel. I was referring to the necessary hack in place to work Java in a non-threaded OS.
The only thing Java is still "slow as hell" with is GUI on Linux. I've run plenty of tests vs C++, Obj-C, Perl, Python, etc. on non-GUI implementations of the same spec (proprietary in-house infrastructure spec).
GUI on Linux is slow for one reason: the linux implementations of Java pre-2.6 linux kernel has avoided the POSIX threading (because it had to) and used processes communicating through shared memory instead of operating from the same address space. This is most significant for GUI apps because in Java each Listener runs in its own Thread.
IF Sun releases a true thread-using implementation for linux you'll see a BIG performance gain on the GUI and maybe some gain elsewhere as well, but in the meantime I have to request (again) that folks not dump on Java unless they've used it within the previous year.
My $.005
I'd like to be able to get cable internet without having to pay for TV at all.
I wonder if that's because only God could be so cruel...
Microsoft has a very long future developing games. For linux. :)
Seriously, what other software could be sold when so many people are developing free alternatives? Games are the last proprietary software the world will ever see (since the primary component is in the design and not the actual code). It's more like art than software in that respect.
So welcome, Microsoft, to your niche. You'll find that the next generation of X-server that supports sound and openGL a joy to work with.
The biggest reason that Java is a resource hog on Linux is that it's current implementation is a hack. Using shared memory segments to communicate between process threads is not how the runtime was intended to be implemented. Now that 2.6 has *real* threading, we'll see what Java can do in Linux with green threads. I think many people will be surprised. (I've personally surprised a few Java bigots where I work by outpacing their C++ and Objective-C code with Java solving the same problems, but that's a single-threaded server process with no GUI.) IMHO, Java is the right direction, and gcj is my greatest hope.
1. invent ridiculous but unassailable theory (you can't prove me wrong - nyah, nyah, n-nyah nyah). 2. WRITE BOOK 3. Collect $$$ had to be said.
One comment: for a company of IBM's size, two years is a VERY short time to switch every desktop to a different OS. I work for a much smaller company and our estimates are that a switch like that would have to happen in a phased implementation over AT LEAST two years.
Unfortunately 98% of people vote for whomever's message was repeated the most times while they enjoy their post-dinner coma in front of the television each night. So I predict that the winner will be the biggest spender on television advertising. Internet usage typically requires thought (and, oh my! READING), so it's much less effective.
Those big entertainment centers with the deep shelves make great storage. Put two or three in your office and it will become more pleasantly dark too.
From all I've heard, EJB is for LARGE projects. $2,000,000 is not a large project.
Psion has never actively pursued the consumer market; they consider the enterprise to be their niche. In some ways, the device is more rugged than other alternatives, and with no HD you do have increased battery life without an extra extension battery. The new model also boasts the ability to store things you don't want to lose in a total power failure on an internal flash card (which is nice in comparison to the original netBook that had no internal persistent storage). I don't at all prefer CE.Net, and would have liked to see them at least offer a port of Linux, but I guess there's business decisions that overrule technical ones.
I'm glad someone else sees Dick for what he is.