Chris Abbey writes:
> umm... no, not really. I don't think I represent a small segment of the
> Java world when I say "give me stability over new features". Or worded
> differently (from a bug traq on the JDC) "stop dreaming up new APIs and
> finish fixing the ones you dreamt up last release".
Well stated. Unfortunately, API bloat is considered to be more
important for Sun's strategic interests than fixing the core
technology... and given the average consumer, they might be
right, short term.
Personally I have no sympathy for anybody who started bugging the
Blackdown team about Java3D of all things. There was an excellent
product, Magician, that supported more platforms than Sun ever
could or would, included Linux all along, sold cheap, came with a
truck load of demos and samples. It got taken off the market
because of all that mindless "Gimme JavaD3" instead of educating
yourself about your choices.
> java development isn't like other linuxian projects. It isn't
> OSS, it isn't GPL, it isn't something anyone can go out and grab the
> sources to and hack. It can't be.
Beg to differ. One reason to be grateful to Sun is that they
published specs, and that their legal position allows for clean-room
implementations. This is exactly the situation in which OSS/GPL
thrives - a clear cut goal, a set standard to implement. Japhar
and Kaffe do exactly that, and in a few more years time they
will offer the stability (but still not the then most recent
features). OSS might not be capable of inventing a technology
like Java, or pushing it, but it can sure clone it once defined
and established.
If somebody still isn't convinced the situation could be much
worse, browse the revision history of the Wine project, and
contemplate Java being defined by Microsoft.
b.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
