Jonathan Schwartz, the executive vice president of software at Sun Microsystems Inc., has been swamped with requests for him to clarify and expand some of the comments he made in a recent interview with eWEEK Senior Editor Peter Galli. Here are his expanded thoughts about the companys Linux strategy, its Solaris operating system, its support for the open-source Linux operating system and its indemnification policies.
Our Linux Strategy
The issue that keeps me, and our customers up at night isnt whether we have a Linux strategy—it is whether we have a Java and Web services strategy. Customers ask me all the time “where should I be building applications and developing skills?” C or Posix dont make any sense as a target, at least for enterprise applications. Java and Web services do make sense—for obvious reasons. Firstly, theyre portable, based an open standards (rather than standards determined by volume distribution—which is the problem the Linux community is increasingly facing as dominant distributions move in directions the community doesnt want. Secondly, because theyre open standards, you can move applications from one suppliers implementations to any other. Open standards enable substitutability—and competition. Markets determined by volume alone are subject to tipping—witness Windows, and what happened with the browser world. Because Microsoft was the dominant supplier, it controlled the market, and now its telling the world which Web sites will render in IE, hiding behind the Eolas suit. No amount of standards can influence the Windows world—the Java world works differently. Participants agree to a standard, then we ship it.
Tipping is already occurring in the Linux world, and I am worried about it. For example, personally, Im a big fan of Debian—I think it tries to keep the industry honest. But I dont see any enterprise ISVs qualifying to/supporting it, which removes it as an alternative for those whove grown tired of price increases from dominant distributors. Ive watched a couple enterprise customers try to move to Debian, and fail for lack of ISV support. So now those customers are stuck. But again, this is the server—the clients a different matter (see below).
We have our own operating system, its called Solaris.
I know this statement bothers some in the community. Back in 1993, the world told us to abandon Solaris for Windows, that Microsoft would take over the world. We disappointed Wall Street and some customers by staying our course with Unix, with Solaris. Thankfully, we didnt blink. You cant even name the companies that did—they no longer exist. So were doubling down on Solaris, and focusing on adding value and innovation. Were one of the three remaining operating systems in the world that runs on 32-bit and 64-bit systems.
But thats not an exclusive contribution. Remember, Sun founded itself on open source using BSD. We totally believe that open-source development can foster a wellspring of innovation and community—weve built our company on the premise (remember NFS). This does not mean that everything can or should be open source. Sun continues to pursue a hybrid model in which we use and contribute to open source when that solves customer problems—we are a massive contributor to the open-source community, and well continue to innovate with our own IP. Theyre not in conflict.
Having our own operating system gives us the ability to solve customer problems using the best technology available and be agile to as well as drive industry changes. We can guarantee road maps, ship dates, and predictability and ISV support. Enterprise customers who come to Sun get the best-supported products and can take advantage of open source, and packaged products without concern.
And for those that want either Red Hat or SuSE, were happy to supply it—but our role is as a supplier/reseller. Well deliver our products atop them where customers seek it, and absolutely add value to help promote Linux and Solaris as an alternative to the Windows world—but our operating system investments will target Solaris, on Intels 32-bit x86 instruction set, on AMDs 64-bit Athlon/Opteron, and on Suns 64-bit Sparc.
Unlike IBM, we will not move away from having our own operating system. We believe that in so doing, in effectively end of lifeing AIX by not shipping it on x86, IBM has left itself exposed to the dominant distribution, whose objectives arent necessarily aligned with IBMs. On Intel, then, its down to Microsoft, Solaris and Linux.
Where will Sun support Linux?
Computing is a very broad market, from sensors to supercomputers. We have no interest in abandoning our existing Solaris customers, or in ceasing to grow the volume market for Solaris on servers. Were making massive performance improvements on 1 and 2 cpu Intel and Sparc systems, growing our ISV base, growing value and functionality with the complete Java Enterprise System—which delivers value on both Linux and Solaris. Our strategy is to make Unix successful, whether its Solaris from Sun, or Linux from the community.
But on the desktop—and moreover, on devices—its a different world. I dont expect to see anyone running Solaris on a mobile phone. I do expect those devices, and many desktops, to run Linux—and with Linux, comes Java, and higher level programming abstractions. So were very interested in protecting customers and OEMs from the legal issues surrounding Linux to help promote the evolution and deployment of new client devices, especially those running Java. Our newest desktop is built atop Linux and Solaris, and at $100/desktop, or $50/employee, delivers real value against the alternatives—we obviously dont get there with Java alone.
Linux plays a strong role for us in devices—we dont necessarily have a Linux strategy, per se, because thats at too low a level, but we do want to see Linux succeed. Java and Linux are entirely symbiotic. With their success comes market opportunity for everyone. The combination of the two preserves open networks, and provides customers with choice and competition. Thats goodness—so let me be unmistakably clear: we think Linux redefines the landscape for competitive alternatives where none previously existed. On the desktop, there has been no x86 alternative for more than a decade. And we are driving that as aggressively as possible. Alongside Solaris for higher power markets, and not in replacement of it.
Folks are confusing indemnity with warranty—warranty is all about a vendors ability to attest to a products suitability or fitness for purpose. Indemnity is very different&&151;its the guarantee a vendor provides its customers that in the event a third party sues the customer for using its intellectual property, the indemnifier will cover the risk. Sun provides indemnity for all its products, and we believe that confidence and security matter to enterprises building their business on our products. That IBM and Dell refuse to offer indemnify suggests theyre using the community to harvest revenue, while leaving risk with those who contribute to open source (who may not get paid), or those who use it (and dont get any protection). Its a real issue—and Sun will protect its customers, and vouch for its products. That Dell and IBM wont vouch for Linux strikes me as hypocritical—especially for IBM, the industrys most pernicious patent litigator—they derive huge revenues from suing companies based on the claim theyre using IBMs technology. IBM doesnt talk a lot about that. And now theyre saying they wont offer any level of formal protection for Linux customers, that they dont need it. On the one hand theyre suing companies based on claims of stolen IP, and on the other, theyre delivering products and refusing to give customers the security that IBM stands behind the intellectual property. Maybe its me, but I dont understand. From what we hear within IBM, their patent folks dont understand, either.
We are committed to driving solutions for customers—solutions that meet price/performance objectives, security, and feature/functionality. Based on open standards, based on a history of innovation, and an unparalleled—and unquestionably honest and forthright—participation with the developer community.
I hope that helps clarify my statements. As always, Im open to input from the community. We would be nowhere without them, and we count on their support (and critique) to shape our thinking and strategies. Even when we, with respect and deference, disagree with them.
Discuss this in the eWEEK forum.