Wednesday Jan 23, 2008

Notes from Disney World

Call it fate or karma (of course, I wouldn't) - or just a lot of hard work to make it all come together in a very short timeframe - but we were incredibly fortunate that MySQL kicked off their annual worldwide all-hands meeting on the same day as Sun's acquisition announcement. Florida's Disney World was the optimal travel location for the globally distributed workforce that is one of the fundamental tenets of the MySQL organization. Collectively we thought that having a group of Sun folks participate in their meeting and discuss why we're all so jazzed about our joint future would be a great idea.

So a number of us headed cross country late Tuesday – James, Ian, Eduardo, Bill, Karen and others checked in to the Magic Kingdom just prior to Jonathan's announcement.

Marten presented the news at the opening of the Wednesday event – coinciding with the public press release outlining the details of the arrangement. Jonathan, by satellite (we had another long-planned partner event in CA) spoke interactively with everyone and outlined our plans, our hopes and our dreams in bringing these two companies together. Together they made clear why I am absolutely certain that this will be a world-changing event and a win for both companies, our joint communities and our customers. And all of us at Sun are absolutely committed to that outcome. Absolutely. Of course, I'm required to say the acquisition hasn't closed yet and its completion is subject to regulatory approval and other customary closing conditions...

Then it was my turn to give my perspective as the leader of Sun's software organization - which is soon to include the MySQL team, to be led and directed by Marten... with his role unchanged from his current purview and responsibilities... now part of the software leadership team... and also part of Sun's Executive Management Group.

I'll skip the details – because this was an 'in family' conversation. A new, expanded family. But family nonetheless. What I said can be summed up with these two slides:

MySQL and Sun Cultures


MySQL and Sun Customers

The two pictures speak volumes on why this is such a perfect match. Throughout the diligence process, in discussions that connected MySQL's team with many of the folks cited above, there were times when we each felt we were looking in a mirror. Our work style, open source models, community and contribution ideology, licensing priorities, business models, technical excellence, innovation focus, sales and service plans, have so much in common that it was almost eerie. But at the same time, the scale of our combined developer and customer base will be dramatically broadened. We'll more than double our customer list and multiply our opportunities.

For the community, in case you haven't noticed, our open source licensing plans center around the GPL V2 for now – as we've done with Java. Same as MySQL. Marten and I have each - independently - spoken publicly about our future interest in GPL V3. Match, match. There couldn't be a more powerful thing that aligns us. Now and in the future.

And for the skeptics who fear that Sun will change, dilute, dismantle, disrupt or otherwise make a mess of things here, clue in. We've changed. You've all seen it. Open source, partnerships, multi-platform, multi-microprocessor, multi-vendor, multi-OS. Same applies here.

We so get it – we are all totally aware of what happens when you kill the goose that lays the golden eggs. So we're going to keep this goose happy and healthy for a long, long time. Promise.

Thursday Aug 09, 2007

Score Another for Clarity and Transparency

One of the joys of my role at Sun is that it provides me a fabulous vantage point for observing the trends and patterns of our industry, while personally having earned the perspective of time to compare historic and current events, and thus to note the distinction between the relevant, the immaterial and the curious. I've also had the good fortune of being in a unique position during Java's decade-long journey of ever-increasing access, openness, transparency and opportunity.

Beginning in 1995, Java source code was made available under a research license. Shortly thereafter, Sun led the creation of the JCP—comprised of partners representing commercial, non-profit and academic interests—to share in directing the evolution of the Java platforms. And the rest, as they say, is history. Java is now the most popular and widely distributed software platform. And, despite the fact that we're all so accustomed to the following truth, that Java has earned that preeminent position in every aspect of the network computing universe—servers, desktops, laptops, mobile phones, set top boxes, embedded devices, smart cards, transactional systems and digital media, is all the more remarkable.

It was May of 2006 when Jonathan and I announced to the crowd at JavaOne that Sun would release Java technology under an open source license and, following words with deeds, Sun began doing so last November. We clearly defined the platforms—Java SE, Java ME, and Java EE, and the license—GPLv2, much to the delight and surprise of many, including the Free Software Community. This action was the culmination of a series of careful steps that Sun had been taking to open up our development processes—creating a community development process for the JDK and open sourcing our Java EE implementation under the CDDL license, which will remain under Project Glassfish as another license option for developers.

Throughout this journey, I've slept well at night knowing that Sun has done our utmost to balance the priorities of open source communities along with the responsibilities and obligations that we have with the myriad of enterprises, individual developers and consumers who have invested in the promise of "Write Once, Run Anywhere". The choice of the GPLv2 license was and is key to this balance, because it takes away the potential for a closed fork of the code, ensuring that we can all maintain compatibility. This simple, singular and unambiguous decision was made to protect the freedoms of all participants in the Java ecosystem, ensuring that innovation remains in the open, and creating a bridge between the existing Java ecosystem and the world of GNU/Linux. With these two communities working together, the scale of creativity and opportunity will lead to innovations that will no doubt dwarf those we have seen to date.

So today we're taking the next step—one I discussed at this year's JavaOne conference. Sun is making the Java SE JCK—the TCK compatibility tests that determine whether an implementation faithfully conforms to the Java SE specification—available to the Java GPL software community using a license that continues to protect the Java compatibility promise while respecting the values of free software. This means that OpenJDK implementors, including GNU/Linux distributions can test free Java implementations based on code released under the GPL in the OpenJDK community, and validate that their implementations are compatible with Java. We're empowering distributors of free Java implementations to be part of the "Write Once, Run Anywhere" promise, while fulfilling all of their obligations under the GPL.

The TCK is a conformance test. It’s the single authority against which everyone tests, and of course, a conformance test that could be altered would have neither value nor trust. So the tests are fully available for learning from the code, and running against OpenJDK-derived GPL’ed implementations, but the license doesn't allow for changing the tests. Anyone who flunked their first driver's exam probably wished then that they could change the test to conform to their mistakes, but the rest of us on the road are all glad that is impossible.

We knew when we chose the GPL and the free software model for Java technology that we couldn't satisfy everyone's desires. This is the case for the Apache Harmony Project at the Apache Software Foundation. The Harmony Project has applied for a license to use the JCK under the JCP's Scholarship Program for qualified not-for-profit organizations. Sun has offered Apache Harmony a license to use the JCK and the Java Compatible logo at no charge once their implementation passes the tests, and we’re even offering free support to help Apache run the JCK. But because the Apache code is not governed by the GPL, and does not require code sharing by any entity using or modifying Harmony, the terms of this license are the same terms under which Sun licenses the JCK to commercial entities that build their own independent implementations of the Java SE platform. As was made clear in their open letter to Sun, the ASF is not satisfied with these terms.

For what it's worth, I completely understand why there is disagreement. There are fundamental principles and goals that separately define the GPL and Apache Software Licenses. Unlike the GPL, the Apache open source license does not require innovation to remain in the open. Java technology governed by the Apache license could be altered by any organization—commercial or non-profit—and rendered both incompatible and inaccessible to the community. The trust and value of “Write Once Run Anywhere” could not be upheld.

And this is simply different from what we have articulated as a goal and a priority for the Java platform for more than a decade—because compatibility matters, and our communities expect us to keep their work in the open as Free Software.

But I would be remiss if I didn't clearly state the relationship between Sun's open source programs and our customer, employee and shareholder responsibilities. Sun is first and foremost an innovation company. It is what separates us from other organizations that vend commodities or directly leverage the innovation of others. I'm extremely proud of our accomplishments and take significant pride in ensuring that those associated with Sun realize the benefits of those virtues. No other large organization brings together the concepts of open source contributions, large-scale innovation, and rewarding shareholders. Sun is leading a grand scale change in the software industry—and I’m very pleased with the results. With Java as a prime example, we are making our software freely available, to individuals and institutions, both commercial and non-profit, under the clear terms of the FSF—the GPL. We believe that “copyleft” is both unambiguous and instrumental in fulfilling goals of both communities and commerce.

Sun believes it is of paramount importance to secure trust in all communities—be they open source or enterprise—by being absolutely clear about one’s plans, intentions and motivations. Thus we will have to agree to disagree on this point with the Apache Software Foundation.

So to be clear, anyone—yes, even Sun’s competitors—can use the Java GPL source code for anything—yes, even a fork—as long as they publish their modifications under the GPL—no other consideration required. They can use the TCK to prove to themselves and the community that their contributions do not alter the promise of compatibility. But access to the code, the tests and the ‘Java Compatible’ brand governed by any other OSS license is both outside of our pact with the community, and not in Sun’s best business interests.

In the 2002 letter that authorized the creation of the TCK Scholarship Program under which Apache Harmony has applied for their TCK license, Sun acknowledged the desire of the Java community, and the Apache Software Foundation specifically, to create independent, open-source implementations of Java standards under the auspices of not-for-profit open development communities. Apache and others have done just that over the intervening five years under the scholarship program. For example, Apache has successfully used the Java EE TCK to certify its Geronimo project and compete against others like the JBoss community and Sun's own Glassfish—Java EE Application Server. Let's not lose sight of the big picture—Java is free and open. Sun continues to contribute both code and development efforts to many Apache projects such as Tomcat, Roller, River (Jini), HTTPD, and Derby.

Sun has now fulfilled the dream of free, open and compatible Java. I'm passionate about the value and virtues of free software and we've proven it—our most valuable assets are now open source. The path is open for completely free and compatible versions of the Java platform to be shipped with operating system distributions of all kinds. I encourage everyone in the open source communities to look at the new OpenJDK JCK license and let the team know how well it works for you.


Thursday Jul 19, 2007

Who Woulda' Thunk?

Of all people. Who woulda' thunk?

Tuesday May 08, 2007

This Time It's for Everyone

Back in the day, I had a dinner meeting with an old friend leading the UNIX OS work at another Silicon Valley company. These were the early Mosaic days—and I had just come off a long run, at my Sun workstation, of surfing and looking under the covers—so I could appreciate exactly how it all worked. As was (and is) my wont, I was raving about the brilliant simplicity of it all, when he stopped me in my tracks and said something to the effect of, ‘it will never really work’. He went on about the lack of referential integrity, unmanageable navigation techniques, and on and on.

We know how that chapter ended. And why? Peeling away all of the artifacts of history, the simple truth is that the access and simplicity of the web enables the expression of a fundamental component of the human machine—the need to communicate. As powerful as is the visceral impact of staring at fire, or the soothing sounds of the ocean surf, humans have, deeply encoded in their DNA, the need to communicate. That compelling drive, and to do so as richly and as broadly as possible, is a force more powerful than the limitations of distance and the jurisdiction of governments. And any technology that is a catalyst for the fulfillment of this deepest of human traits will overcome the limitations of technical imperfection. In effect, to harness our machines to make us all more human.

I was meeting with folks in the Java organization recently—discussing our final plans for JavaOne—and reviewing how all of their hard work had come together for today’s remarkable announcements. It was the culmination of many such sessions where I had been raving (again, my wont) about the potential opportunities for the Java platform. Yes, it’s the most pervasive software platform in history (more than 2 billion mobile handsets and more that 70 percent of all desktops and laptops), and yes, adoption just keeps accelerating (52 million desktop/laptop downloads in January) and yes the number of developers continues to grow at an astounding rate (did I mention more than 6 million strong?). And yes, in open source form under the GPL license (a process completed today) there will be yet more access via Linux distros and more contributions from everyone.

But the ability to deliver a rich experience, and tap in to those individuals who have the greatest creative skills, drove us all to realize that there was much more to do. As successful as the Java platform has been, it has catered to the needs of the technical developer—so rich and broad in scope that rapidly expressing a media-centric experience—and doing that quickly and simply—was beyond the reach of those with the interest and expertise to do so. Similar to the design tradeoffs of my long-ago dinner, we had made remarkably complex things possible—from server to desktop to mobile device—but simple things unapproachable. Too much assembly required—from complex user interface design to the source code porting of the JRE to mobile devices. We had to address, no attack, the opportunity of enabling Java to be the mass communication platform that we knew it could be.

Which is why we created JavaFX. A family of products, technologies, and soon, opensource communities, to radically improve the networked communication experience for people at a worldwide scale.

We created a new scripting language, JavaFX Script, that targets creative professionals to build rich, stimulating web and network experiences. It’s not Java the language, but it produces portable bytecodes that run on Java the platform. It’s the same platform that has the enormous distribution I cited above, and the same platform that runs applications written in Java and about one hundred other languages that now run on the JVM.

This architecture enables a continuum across development paradigms to create amazing web experiences. Create in JavaFX Script. Drop in to Java (or JRuby, or, or), access all of the libraries in the JDK. And do it fast. Very, very fast.

Then we created JavaFX—a line of products designed around JavaSE—designed to bring a consistent media-rich environment to every modern consumer device. The first one to roll out—JavaFX Mobile—is a complete software system for smartphone-class devices. Complete from the mobile metal to the user experience and personal applications, JavaFX Mobile runs applications written in JavaSE, JavaME and all of the new content written with JavaFX Script. Thank Moore’s law, the Sun team, and some very smart folks and their technology brought to Sun as part of the SavaJe asset acquisition. WORA. Not just across operating systems or microprocessors. Everything.

Oh, and while you’re taking a closer look—take a look at Derby—the embeddable, pure Java database for consumer devices as well as servers. Use it as a reliable database for new applications, or as a cache to synch your activities when moving from off-line to on-line. Use it with JavaFX. Everywhere.

Oh, one more thing. I just had my one year anniversary back at Sun. Love it.

Thursday Feb 01, 2007

Five Things

OK, OK, I guess it is useless to resist. So, at the risk of revealing far too much about myself, here are five things you probably don't know...about me, that is:

  1. I used to own one of the now-famous GM EV-1 all-electric cars.
    I'm an absolute zealot for innovation and design. I just had to have one. And I drove it every day. It had more than enough range to make it from Palo Alto to San Francisco and back. It was perfect in every way. What else could I need? Particularly when my other “car” was (a very hot) motorcycle. That was the ultimate price/performance leader in adrenaline diffusion and—with the EV-1—the perfect transportation pairing. Ahhh, back roads, high speeds, Highway 1...until I came home one day and noticed the tips missing from my boots. That's when I realized that the risk/reward ratio had dropped under 1.0. Sold it just about the same day. My family was quite pleased. I suspect Jonathan was too.
  2. Contrary to press reports at the time—and once and for all—I did NOT leave Sun in 2004 because of any arguments or disagreements over the Microsoft settlement.
    In fact, I was one of the leading advocates and negotiators of the settlement. And I was/am truly pleased with the outcome. After 14 years, isn't “I just want to do something else for a while” completely understandable? (Oh, by the way, when I came back to Sun after two years at Cassatt, they put me back in the exact same office. Spooky and weird, but I'm over it...I think.)
  3. Undoubtedly like many others in the tech industry, I was one of those kids who used to drive my parents crazy taking apart anything around the house that was mechanical or electronic: TVs, radios, whatever.
    I rewired the intercom, hacked the phone system with boxes black and blue. I also bought one of the first production ICs (oh, how I'm dating myself) and built a cool analog thing. Sooner or later, I'd put everything back together. Sometimes better, sometimes not.
  4. For my first summer job, back in high school, I was a pool lifeguard.
    Greatest job in the world for anyone that age. I kept telling my kids when they were that age (actually, one still is) that you've got to do this. Let me see: one hour on and then one off, in the Sun, keeping an eye out while talking to, um, interesting people standing at the base of your perch. Yeah, there was the occasional diaper thing, but I also registered one actual save. Priceless.
  5. I worked for Sun's first OEM partner—a company called ComputerVision—back in the Boston area.
    Always a software guy, I was one of the people on the team that chose between Apollo and Sun as we migrated from our proprietary systems. And the rest, as they say, is history.

So for my personal edification and the joy of interrupting people with already busy lives, let me name a few friends, associates and luminaries to share in the joy of being tagged:

  • Mike Dillon—General Counsel and Corporate Secretary at Sun—and one of the very few senior people in the legal side of the industry who is both brave and creative enough to blog. This man single-handedly takes the wind out of every lawyer joke ever told.
  • Rob Gingell—CTO of Cassatt, Sun Fellow Emeritus, Sun Chief Engineer Emeritus—a perfect example of why working in our industry, with people like Rob, is a joy.
  • James Gosling—What do I need to add?—other than ditto the last part of the above.
  • Chris Shipley—Producer of the DEMO conference—has a great eye for the new, cool and relevant.
  • Steve Wilson—Head of our Sun Connection programs—doesn't ever sleep, so he can knock this off, day or night.

Friday Jan 26, 2007

Sun and Intel: A View from Russia

It was a big, big news week here at Sun. Sometimes those of us in the tech industry think that the events and announcements that we create are really something—but in fact they turn out to only be a big deal for ourselves.

This one was different. The Sun-Intel partnership over Solaris OEM distribution, partnering on Java, and Intel's support for NetBeans and Java really was a worldwide event. I know this because I had a long-standing business trip planned to Russia and the Czech Republic that coincided with the announcement. So I took part in the event while in St. Petersburg and saw firsthand how the news resonated with press and customers there, as well. This was clearly big news on a planetary scale.

Of all the things we announced, there is one topic that received limited coverage, but is just as relevant for those developing on and deploying Solaris—and that's the Sun Studio compiler technology. Part of the agreement is for Sun and Intel engineers to work closely to further optimize the Sun Studio developer environment. This means that code developed for Solaris on Intel's new chips, compiled with Sun's tools, will absolutely rip. It already does, in fact. Many benchmarks show Sun Studio compilers are already the fastest production compilers for Intel, Opteron and SPARC. Oh, and did I mention that you can get those same compilers with the same performance and dependability for Linux, as well?

So in case you weren't paying close attention—or were in a spot on earth where smoke, rather than copper or wireless, is used for communication—it boils down to more great hardware—this time based on Intel chipsets—is coming from Sun, courtesy of the genius of Andy Bechtolsheim. In partnership with Intel, we'll further adapt and optimize Solaris for Intel systems—servers, desktops, laptops—including more and better driver support, better native compilers and tools, a partnership to tune Java performance for new chipsets, and Intel's endorsement and OEM distribution of Solaris.

Those who still question whether or not we are deadly serious about providing our world-class open source Solaris OS technology on the highest volume platforms in the world, just ask someone in Russia.

Wednesday Jan 17, 2007

All the News That's Fit to Print

I love finding out what I'm doing by reading trade publications. According to eWeek, apparently we're going to license OpenSolaris under GPLv3. I have to say I was surprised because it just ain't so. This is primarily due to the fact that the terms of GPLv3 aren't final, thus making it impossible for us to commit to it. It would be like signing a contract with blanks to be filled in later. So, with all due respect to eWeek, I feel I have to go on record to say the article isn't correct.

However, while I'm on the subject, let me repeat what I've been saying since we issued Java under GPLv2. We are in active discussions with the community regarding the detailed terms of GPLv3 and I'm very pleased with the current course and speed. As v3 is finalized, we'll work with the community to give very serious consideration to dual-licensing OpenSolaris (under CDDL and GPLv3). Until it is completed, we just can't make a commitment. And you wouldn't either. So, I'm afraid that on this particular topic, this is a no-news day.

On the other hand, it was a big news day for Solaris. Check out these stories from ServerWatch and InfoWorld.

Monday Dec 11, 2006

Java SE 6 is Here

Today we formally released “Java Platform Standard Edition 6,” aka Java SE 6.
And although there was more than a little excitement last month about the release of all of Java under the GPLv2 license, this too is big stuff.

Actually it's bigger because it's the proof that developing Java in the open will not only work, but will yield better results than ever before. Java SE 6 is the first version of Java technology to be developed from start to finish as part of a community development process in which Sun released weekly snapshots of the complete source, binaries and documentation for JDK 6. These raw, early access snapshots let external developers review and contribute while the JDK was being developed. More than 330 external developers took part in the process but the code and info was available to everyone. Net-net: We think that makes this the best version of Java ever.

As the precursor to a completely open source community development model, we learned a lot here that will move the GPL program along more quickly—community building, source management, governance—all things that are in the works right now.

But it's the code that counts, and that's now final. And to make this all more valuable and accessible, we revamped NetBeans to support all the new features of Java SE 6. It has better visual tools and better native development capability for building out the next generation of Web applications. Again, we think it's the best IDE for making Java SE 6 developers more productive.

Besides the great work done by the Java community, inside and outside Sun, in getting us to this milestone event, I also want to thank the folks at Microsoft. Yes, that's right—Microsoft. The interoperability teams at Sun and Microsoft worked together to ensure Java SE 6 will work with Windows Vista. As SE6 becomes the standard distro on PCs worldwide this teamwork will ensure the best experience for consumer and enterprise Java users.

So go get it here at:

Now with that done, it's time to look forward. We're at an inflection point right now—with Java, global communities, bandwidth, Web2.0, time-based media, DRM, and on and on. When we imagine what Java should be going forward, I'd like to hear from you.

Monday Dec 04, 2006

An Update on Open Java

We have been utterly overwhelmed by the positive response to the announcement that Sun would put Java under the GPL license. This was a complex milestone to achieve and the fact that it drew such accolades from the open source community, customers, and technology and business analysts alike is another sign that Sun has defined the right software business and technology strategy.

Since the announcement, I've realized there are a couple of points we need to clarify. First, I feel obliged to acknowledge that I misspoke during the announcement. I referred to Richard Stallman, founder of the Free Software Foundation, as the “father of open source.” But it's not about open source, which is a legal or contractual distinction and a means to an end. It's about freedom—for developers, systems administrators, consumers—to create and innovate with as few restrictions as possible. I believe we made that point loud and clear: The release of the first open source Java code is a means to the end of fostering new technology solutions.

Another clarification: Although almost everyone was positive about the choice of GPL—even while many were in stunned disbelief—we got a lot of questions about Sun's choice of GPL version 2, as opposed to v3. Just to be clear: v3 is in the late stages of definition and approval. It's impossible to release anything under v3 today. However, a number of folks from Sun, including Simon Phipps, are actively involved in discussions with Richard Stallman, Eben Moglen and others regarding the terms and nuances of v3. So for now, v2 is our first choice for Java but, depending on the final terms of v3, it need not be the last.

Finally, I'd like to once again publicly thank the team at Sun that has made Java so remarkably successful. The numbers continue to climb—4 billion devices of varying scale, bundled on more than 70 percent of PC desktops, 80 percent of all mobile phones. These indicators maintain a positive and improving slope. These are great folks who worked tirelessly through unbelievable complexity created by a perfect storm of challenging technology and even more challenging communities, corporations and legal issues. James Gosling and Graham Hamilton are the names most often cited. Add a few hundred more, and you're closing in on the complete list.

Monday Nov 13, 2006

Green Field

Our older son turned to a new chapter in his life this fall – leaving the nest and going to college. He's a great guy and we're all very proud of him. But as a parent, you hold your breath nonetheless, looking back fondly at the years past, hoping we did all things possible to prepare him for the days ahead, and with excitement and anticipation of just what the future portends.

You spend a large piece of your life helping him prepare for the day. Never wanting to unwrap our arms from him when he was young, but each successive year sharing him with the rest of the world, influence increasingly coming from events and individuals outside our control. Until the day comes that we're just a part of his very rich life. Always there for him and and forever driven to ensure his success and happiness. He came back to visit for the first time a few weeks back. Already more worldly, more confident and secure. It was a wonder.

At the risk of anthropomorphizing the abstract, today's Java GPL open source announcement marks a remarkable new chapter for many constituencies – for developers at a global scale – inspiring Brazilians, Indians, Chinese, Russians, Africans, Americans – everyone, to freely build the products that best characterize local opportunity, leveraging the best global technology; for Linux distributors – who want Java to be part of their offerings but have required an impedance matched license; and to deployers and administrators worldwide – who are basing their infrastructure increasingly on open source and GPL and now can move ahead with Java unfettered.

The individuals at Sun are a passionate, driven and brilliant bunch of folks. No better evidenced than the group of people here who have led our Java programs through the years. In the early days we were heads down and all alone. It was our job to nurture and protect Java in its formative years. As interest grew, we found ways to share both Java's value and the ability for all to contribute. When some would try to violate the covenant of access and compatibility, we defended it, aggressively, and triumphed. And Java blanketed the planet – an industry with a combined value greater than 100 billion dollars with more than 4 billion copies distributed worldwide.

And we're nothing if not consistent. With Netbeans, OpenOffice, OpenSolaris, and now Java, Sun is now the free software movement's most significant benefactor. When I came back to Sun, and met with James Gosling and a few others in my office, I asked why we should use anything but the GPL. It's good for developers and it's good for our shareholders. More developers, more creativity all done visibly in the community. And larger markets, with Sun helping to fuel the future.

For the many who have helped Sun write the first part of this new chapter by feeding, nurturing and guiding Java, thank you. And for those who said Sun would move slowly, err, or not do it at all, I'd be happy to get you a fresh set of tea leaves. Releasing our Java technology with the GPLv2 license is an event like few others in the history of technology. Take a look at comments from across the community to hear what they have to say. And we're all thrilled and excited – sending Java off and affecting the world on a grand scale, expecting only the best things but knowing that, in the capable hands of every interested developer, we're now just a part of a very rich future.




« February 2017