Wes Biggs wrote:
> > All your arguments are factually right. But pyschology is at work here, and
> > especially in an extremely important project like JDK porting (from my
> > perspective, it is the second most important project after the kernel and at
> > times more important), you have to acco
Wes Biggs wrote:
> > All your arguments are factually right. But pyschology is at work here, and
> > especially in an extremely important project like JDK porting (from my
> > perspective, it is the second most important project after the kernel and at
> > times more important), you have to acco
I think the more relevant (and pragmatic) question is: What can we do to
make the Blackdown team status more visible? Clearly many questions and
concerns would be eliminated if the web pages had a regular status update --
this would help you to fend off flames and persistent questions as well.
I
On Wed, 21 Apr 1999 10:18:36 -0700, Wes Biggs wrote:
> [...] they've [Sun]
>*increased* Blackdown's time-to-market by requiring JCK compatibility (I'm not
>arguing that this should be eliminated, just that this is the effect it has had).
That is not really true - Yes, passing the JCK is extra wo
> All your arguments are factually right. But pyschology is at work here, and
> especially in an extremely important project like JDK porting (from my
> perspective, it is the second most important project after the kernel and at
> times more important), you have to account for psychology, whethe
Chris Abbey wrote:
> How so? You're multi-billion dollar international corporation is staking
> it's bottom line on java2 for Linux? You were asssigned a project and sold
> your prof on the idea of doing it on Linux and in Java, but absolutely
> _have_ to have the latest and greatest whiz-bang fe
