Gervas Douglas wrote:
> Java, on the other hand, has probably turned out a far greater success
> that a hardware-centric company like Sun could have dreamt of - as we
> all know. That does not mean that political and psychological factors
> outside the control of technical arbiters would always make it
> acceptable in a given situation.
Gervas, I truely know about and comprehend the cause and effect cycles of the
best technologies not winning. What I don't understand, is why many feel
comfortable with that happening.
Jini, wasn't really ready for the mass market until JERI was in place in Jini
2.0. That release has all of the things revolving around security and
configuration that make it possible to have much more automated enterprise tool
suites for development and deployment.
We still get posts on the Jini-users list that mention that they hear Jini is
for "device drivers" and other low level interfaces. So, yes, the Sun
marketing, was really bad. The Sun engineers didn't have a say in the
marketing
strategy. They complained, and have tried to recover, but it hasn't been an
easy road, because they can't easily undo the harm done in the past.
Life keeps changing how we get to look at things.
> We all know people who in certain situations prefer alternatives. This does
> not mean that they are necessarily naive or childish.
I don't recall hearing any stories from anyone who implemented a working Jini
system with solid technical reasons (which there are some) why they couldn't
use
Jini. The majority of people that I've seen on blogs or heard at JavaOne or
elsewhere put down Jini in favor of something else have made very naive and/or
childish arguments.
I'm not summarily saying that anyone not using Jini or not trying Jini has
those
characteristics. I'm saying that so far, I haven't had significant feedback
presented to me on the Jini technologies that makes the case for totally
ignoring them.
If there is such feedback, I'd love to hear it. Dan Creswell (and I to some
extent) have been trying for years to figure out what tools or documentation is
the biggest roadblock to Jini's acceptance. Dan's created a lot of tools and
documentation to fill the gaps that he's realized as important.
The biggest problem that I see right now is that the "industry experts" are
pushing XML because thats where all the competition and money is at. So, we
get
into these battles of whits and words over things that really should be about
technology.
Technologies should improve our lives, not just put a new face on the same ugly
wrappings...
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
