What I'm getting is, because of those non-functional requirements, maybe they get a better performance, better garbage collection or whatever those features are right? But TCK isn’t something customers run, it assures them that the application they run using OpenJDK if they want to switch to Azul JDK is compatible because it's passes the TCK. It means their applications run exactly the same way in terms of their behavior, but there’s different non-functional behavior, meaning performance such as lower latency or faster throughput, etc…Īrun Gupta: That's pretty awesome. Secondly, using Technology Compatibility Kit ( TCK) tests, different distributions of OpenJDK can be verified to be functionally identical to the specifications, making it easy for users to switch without changing or recompiling their code. Simon Ritter: Two things: First, people can create their own implementation of a standard using the specification, like IBM did with a clean implementation for J9. What do you need for that compatibility kit, is it because has multiple vendors of OpenJDK? How does that work? Then there’s a reference implementation (RI) element of it, which is the OpenJDK and 122,000 tests in the compatibility kit because OpenJDK is a reference implementation. So the JCP, the Java community process creates the JSRs, Java specification request which defines the language, the specs, the specification, what the API is going to look like. So OpenJDK is closely linked to the JCP standards, offering a conforming implementation of the standard.Īrun Gupta: Got it. The TCK tests over 100,000 components to verify that an implementation matches the standard. OpenJDK is the reference implementation for Java SE. The Java language specification covers the syntax of the language, the Java virtual machine specification defines its functionality, and the standard class libraries definition offers standard functionality. Each version of Java has a Java Specification Request ( JSR) that includes three components: Specification, reference implementation, and technology compatibility kit ( TCK). The JCP used to cover all standards for Java Enterprise Edition, which have since moved to the Eclipse Foundation*. Simon Ritter: The Java Community Process ( JCP) works to create standards for different aspects of Java. So Sun actually made a standard, which is what led to the Java Community Process. He discussed the concept of a Java standard and emphasized the importance of creating a standard to accompany open source. It took about 10-11 years from its launch for Java to become open source.Īrun Gupta: I remember back in 2006 when, Rich Green, the VP of Java software, announced that Java would become open source. Sun later made the decision to make Java open source in 2006, creating OpenJDK. The Java community process was created in 1997 to establish that standard. As the community started using Java, they requested an open standard and eventually an open source version. Simon Ritter: Java was originally developed as proprietary technology by Sun in the mid-90s. You’ve been with Java from the very first version, has Java always been open source? Their conversation has been edited and condensed for brevity and clarity.Īrun Gupta: Seeing Java evolve over 25 years has been absolutely amazing. They talk about why the “blue-collar” language has survived the shifts in tech, the history of OpenJDK and how you can get involved. Throughout his career, he’s been dedicated to promoting and driving the adoption of Java through developer relations and advocacy. He later worked for Oracle for five years before joining Azul in 2015. In the first event, Arun Gupta talks to Simon Ritter, Deputy CTO at Azul Systems*, who has been working with Java since its beginning, joining Sun Microsystems in 1996 around the launch of JDK 1.0. Follow him on Twitter for reminders on the next one and to ask your questions live. Now you’ve got a direct line to the Open Ecosystem at Intel: Arun Gupta, VP and GM, holds live monthly Twitter Spaces conversations with changemakers in the open source community.
0 Comments
Leave a Reply. |