On Wed, 25 Jan 2012 01:02:16 +0100, Ricky Clarkson
<[email protected]> wrote:
I think the problem is that ordinary code doesn't get that much reuse,
because it can be hard to use a particular class or module outside of
its original intended environment.
E.g., pretty much all the code written by or for my current client
depends on DB2 and on parts of a particular shared schema of tables,
and on their being updated by other parts of the system. There's a
lot of value in some parts (e.g., a job scheduling system in the style
of Control-M) that just isn't transferable even to other parts of the
client.
I think nobody is questioning the point that *some* code can't be reused
(and, I add, that in some circumstances it is not worth while to spend
extra money to make it reusable).
But the previous examples referring to tons of popular Java libraries are
pretty clear to demonstrate that well designed libraries can be reused.
Given that we're basically talking of the Java ecosystem, which I think
most people acknowledge is one of the biggest in the world when compared
to other languages, I think that the conclusion that Java does pretty good
code reuse in comparison to other languages is evident.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
