No doubt there were some community aspects Microsoft did not get!. But now while we're getting things off our chests, isn't it a bit ironic how Microsoft tried to add properties to Java (and since added lambda's, extension methods, nullability etc. to C#) which now here 10 years after is on the table for Java more or less to "rescue" it?
It's clear that Google befitted from hindsight here. So today Google can thank Microsoft for testing the legals and Microsoft can thank Sun (Oracle) for making them captain of their own vessel. The world is a funny place. :) On Feb 14, 3:55 pm, mezmo <[email protected]> wrote: > I just want to get something off my chest about Joe's continued > confusion about the Sun/Microsoft suit and how Dalvek is different. > Microsoft was adding keywords, adding classes to the standard java > libraries, and refusing to support RMI and JNI, adding some custom > classes in the java.namespace to do similar things with COM. Plus they > wanted Sun to thank them for it and allow them to still call it Java. > Google with Dalvek on the other hand has gone out of its way to make > sure that everyone knows that Dalvek is not Java. It doesn't directly > run plain Java bytecode, and if there is a java.* class anywhere it > does pretty much exactly what the original did. For non-standard > extensions, those are in clearly marked android.* packages, which I > personally believe if Microsoft had done, Sun wouldn't have had nearly > as strong a case as they did. -- 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.
