Java is kind of special, in that it mixes these very large lumps combining language, library and runtime/VM. In .NET this is divided up in separate ISO and Ecma standards. The last version of C# to be standardized was C# 3.0 (Ecma-334, 4'th edition in 2006) but work on 5'th edition is underway. The CLR lives under Ecma-335. However, that still have not helped C# very much from being affiliated with Microsoft, even if they actually have less power with Ecma (1 vote, just like other contributors) than Oracle has in the JCP (with their veto-right).
On Oct 5, 2:13 pm, Carl Jokl <[email protected]> wrote: > I must confess that I don't know the fine details of what happened > historically with Java except that I heard that at one point there was > an attempt to make Java and ISO standard but it failed. As I > understand it the establishment of the JCP was done to compensate for > failure for Java to be an ISO standard. > > Is my understanding correct? > > Can anyone shed light onto why Java was not permitted to be made and > ISO standard? > > I find the situation curious given at least one version of C# is an > ISO standard. I am not sure about Objective-C. > > Would Java be in a stronger position if it were an ISO standard rather > than being managed through the JCP? > > Would it help Java if it were not so closely affiliated with one core > company (i.e. more like C/C++ rather than C#)? > > I would be interested in hearing your thoughts. -- 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.
