Re: Java vs C++ speed (IO & Sorting)
Mark Space wrote:
James Kanze wrote:
and second, because of inability to build clean abstraction
layers.
That's the real problem. It makes for a lot of extra work when
using Java in large applications. (For small applications,
Java's actually not too bad. Although I find that once you've
gotten used to programming cleanly, it's frustrating to not be
able to.)
I'd like to ditto Eric's request. Can you elaborate on what you are
referring too here? Is it the lack of multiple inheritance in Java that
you feel prevents designing clean abstraction layers? Maybe it's the
lack of direct interface to system/external libraries (ie, one has to
use Java Native Interface to call libraries with C bindings.)?
Something else maybe?
It has not been my experience that Java in any way impedes the construction of
abstraction layers, clean or otherwise. I find the claim inflammatory at best
that it does.
First of all, no programming language completely lacks the "ability to build
clean abstraction layers", not even freaking binary zero-one machine language,
so let's tone the claim down to one at least marginally supportable. Let's
interpret the claim to be that Java does not support "clean abstraction
layers" as well as C++.
So, what makes abstraction layers clean? In addition to the questions the
others have asked, which are relevant.
Java has never impeded anyone's ability in my direct experience to create what
I call clean abstraction layers, or for that matter, to create clean, useful,
maintainable code that does what its sponsors want with acceptable performance
on time and on budget. I've known quite a few Java programmers, too.
--
Lew