On Feb 17, 2005, at 11:01 AM, Gregory K. Ruiz-Ade wrote:
On Thursday 17 February 2005 08:21 am, Stewart Stremler wrote:In fact, that's the sticking point for a lot of open-source types who complain about the unsuitability of Java -- it's too slow because all array accesses are checked, and there are no pointers to do pointer-aritmetic on. . .
It's too slow because it's actively preventing me from wreaking havoc and
trampling all over my own memory.
I have yet to see a well-engineered Java project that is slow.
I have also yet to see a slow Java project that is well-engineered.
And I have yet to see a well-engineered software project, period.
However, speed is just a red herring. If slow were really the issue, everybody would be using Fortran.
If it touches a network from a personal computer, practically every language is now fast enough. The networks are so slow that the processors are effectively running infinitely fast.
If it is an enterprise network, the O() scaling and parallelism is more important. It doesn't matter what your language is if the performance is O(n^2).
-a
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
