On Wed, 25 Jan 2012 01:31:09 +0100, Cédric Beust ♔ <[email protected]>
wrote:
On Tue, Jan 24, 2012 at 4:23 PM, Ricky Clarkson
<[email protected]>wrote:
My point might not have been very clear, so I'll say it differently.
Parts of Java applications are generally not very reusable. Sure, if
you're deliberately writing with reuse in mind you're likely to write
something reusable, but there's usually too much dependence on
surrounding code
This, by the way, is where COM is very good: it lets you extract one or
more interfaces out of your code that you deem usable by the rest of the
world and it makes this service available at the binary level.
I still can't see the point. I think I need a small example to understand
where C/JavaScript (Ricky) and COM (Cédric) are better.
--
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.
