Slashdot Mirror
Bill Gates Claims OSS Has Poor Interoperability
XeRXeS-TCN writes "In yet another example of Bill Gates seemingly 'not getting it' (or getting it just fine and spreading FUD), he has sent out an email to all MSFT's corporate customers, stating that if they are looking for interoperability, they should not look to Linux or OSS software. What he really means of course, is free alternatives trying to interoperate with Microsoft's non-documented proprietary standards."
Every day, businesses face an ongoing challenge of making a wide variety of software from many different vendors work together. It's crucial to success in streamlining business processes, getting closer to customers and partners, or making mergers and acquisitions successful.
This email outlines some of the work Microsoft is doing to make its products interoperate well in a diverse IT environment; it is one in an occasional series of emails from Microsoft executives about technology and public-policy issues important to computer users, our industry, and anyone who cares about the future of high technology. If you would like to receive these emails in the future, please go to *link removed* to subscribe. We will not send you future executive emails unless you choose to subscribe.
Whether you are connecting with partners' systems, accessing data from a mainframe, connecting applications written in different programming languages or trying to log on across multiple systems, bringing heterogeneous technologies together while reducing costs is today a challenge that touches every part of the organization.
Over the years, our industry has tried many approaches to come to grips with the heterogeneity of software. But the solution that has proven consistently effective - and the one that yields the greatest success for developers today - is a strong commitment to interoperability. That means letting different kinds of applications and systems do what they do best, while agreeing on a common "contract" for how disparate systems can communicate to exchange data with one another.
Interoperability is more pragmatic than other approaches, such as attempting to make all systems compatible at the code level, focusing solely on adding new layers of middleware that try to make all systems look and act the same, or seeking to make different systems interchangeable. With a common understanding of basic protocols, different software can interact smoothly with little or no specific knowledge of each other. The Internet is perhaps the most obvious example of this kind of interoperability, where any piece of software can connect and exchange data as long as it adheres to the key protocols.
Simply put, interoperability is a proven approach for dealing with the diversity and heterogeneity of the marketplace. Today I want to focus on two major thrusts of Microsoft's product interoperability strategy: First, we continue to support customers' needs for software that works well with what they have today. Second, we are working with the industry to define a new generation of software and Web services based on eXtensible Markup Language (XML), which enables software to efficiently share information and opens the door to a greater degree of "interoperability by design" across many different kinds of software. Our goal is to harness all the power inherent in modern (and not so modern) business software, and enable them to work together so that the whole is greater than the sum of the parts. We want to further eliminate friction among heterogeneous architectures and applications without compromising their distinctive underlying capabilities.
This may seem like an obvious approach, but the desire for interoperability is sometimes mixed up with other issues. For example, interoperability is sometimes viewed merely as adherence to a published specification of some kind, either from one or more vendors or a standards organization. But simply publishing a specification may not be enough, because it overlooks much of the hard work it takes to successfully develop interoperable products - namely, ensuring that the "contract" defined by a specification is successfully implemented in software and tested in a production environment.
Sometimes interoperability is also confused with open source software. Interoperability is about how different software systems work together. Open source is a methodology for licensing and/or developing software - that may or may not be interoperable. Ad
He also brought us Microsoft Word, so uninteroperable with itself you sometimes have to use OpenOffice Writer to recover its documents.
Guy asked me for a quarter for a cup of coffee. So I bit him.
ALSA is the current driver infrastructure in the Linux kernel. OSS was the previous driver structure. ALSA has an OSS emulation layer.
ESD (The enlightenment sound daemon) is a software mixer that was also used in Gnome but isn't anymore. ARTS is the basically the KDE version of ESD but it also being deprecated in favor of ALSA's built in abilities like dmix.
I don't see your point.
Time makes more converts than reason