On Fri, 19 May 2006, Chris Gray wrote:
|
| > Open Source java wouldn't be the same if there wasn't some standard to
| > follow and adhere to. If this "standard" is defined rather more by one
| > company than the rest - what is the real problem?
|
| The real problem is that if that company also markets an implementation of
the
| standard, there will always be forces within the company which view all other
| implementations as competitors.
How is this evident - how does it manifest itself?
I do understand that there are some friction, though - "It's _ours_!", and
they're actually right. But java in itself is _nothing_ - it is the
community around it that makes it good.
|
| I don't believe that Fortran or C would would have been better off had IBM or
| AT&T controlled the standardisation process the way Sun are doing with Java.
Those standards
*) mainly concerns the language and not the whole needs of an
application (some basic libs are also standardized, though)
*) took "some years" to develop (C++ - is it standardized already, you
say?!)
*) are tiny, compared to Java SE, EE, ME.
*) are dying. ;-)
.. and probably other things. (Can you compile linux using Intel's or MS's
compiler?)
Basically, what I am implying, is that you'll kill Java if it's taken down
a "true standardization" road (e.g. IEEE, Ecma or similar organizations),
by those processes' slowness ("Internet Time" is at play here..), and
you'll kill Java if it's open sourced, by fragmentation.
.NET has Microsoft as backer, and Java has Sun - and I'm choosing the
latter every day.
Regards,
Endre.
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
