Embrace, extend, and extinguish

The strategy and phrase "embrace and extend" were first described outside Microsoft in a 1996 article in The New York Times titled "Tomorrow, the World Wide Web! Microsoft, the PC King, Wants to Reign Over the Internet",[5] in which writer John Markoff said, "Rather than merely embrace and extend the Internet, the company's critics now fear, Microsoft intends to engulf it." The phrase "embrace and extend" also appears in a facetious motivational song by an anonymous Microsoft employee,[6] and in an interview of Steve Ballmer by The New York Times.[7]

The variation, "embrace, extend and extinguish", was first introduced in the United States v. Microsoft Corp. antitrust trial when then vice president of Intel, Steven McGeady, used the phrase[8] to explain Microsoft vice president Paul Maritz's statement in a 1995 meeting with Intel that described Microsoft's strategy to "kill HTML by extending it".[9][10]

The strategy's three phases are:[11]

1. Embrace: Development of software substantially compatible with a competing product, or implementing a public standard.
2. Extend: Addition and promotion of features not supported by the competing product or part of the standard, creating interoperability problems for customers who try to use the "simple" standard.
3. Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support the new extensions.

Microsoft has claimed that the original strategy is not anti-competitive, but rather an exercise of its discretion to implement features it believes customers want.[12]

• Browser incompatibilities:
  • The plaintiffs in the antitrust case claimed that Microsoft had added support for ActiveX controls in the Internet Explorer Web browser to break compatibility with Netscape Navigator, which used components based on Java and Netscape's own plugin system.
  • On CSS, data:, etc.: A decade after the original Netscape-related antitrust suit, the Web browser company Opera Software filed an antitrust complaint against Microsoft with the European Union, saying it "calls on Microsoft to adhere to its own public pronouncements to support these standards, instead of stifling them with its notorious 'Embrace, Extend and Extinguish' strategy".[13]
• Office documents: In a memo to the Office product group in 1998, Bill Gates stated: "One thing we have got to change in our strategy — allowing Office documents to be rendered very well by other people's browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities. Anything else is suicide for our platform. This is a case where Office has to avoid doing something to destroy [sic] Windows." [14]
• Breaking Java's portability: The antitrust case's plaintiffs also accused Microsoft of using an "embrace and extend" strategy with regard to the Java platform, which was designed explicitly with the goal of developing programs that could run on any operating system, be it Windows, Mac, or Linux. They claimed that, by omitting the Java Native Interface (JNI) from its implementation and providing J/Direct for a similar purpose, Microsoft deliberately tied Windows Java programs to its platform, making them unusable on Linux and Mac systems. According to an internal communication, Microsoft sought to downplay Java's cross-platform capability and make it "just the latest, best way to write Windows applications".[15] Microsoft paid Sun US$20 million in January 2001 (equivalent to $28.88 million in 2019) to settle the resulting legal implications of their breach of contract.[16]
• More Java issues: Sun sued Microsoft over Java again in 2002 and Microsoft agreed to settle out of court for US$2 billion[17][18] (equivalent to US$2.71 billion in 2019).
• Instant messaging: In 2001, CNet's News.com described an instance concerning Microsoft's instant messaging program.[19] "Embrace" AOL's IM protocol, the de facto standard of the 1990s and early 2000s. "Extend" the standard with proprietary Microsoft addons which added new features, but broke compatibility with AOL's software. Gain dominance, since Microsoft had 95% OS share and their MSN Messenger was provided for free. Finally, "extinguish" and lock out AOL's IM software, since AOL was unable to use the modified MS-patented protocol.
• Adobe fears: Adobe Systems refused to let Microsoft implement built-in PDF support in Microsoft Office, citing fears of EEE.[20] Current versions of Microsoft Office have built-in support for PDF, as well as several other ISO standards.[21][22][23]
• Employee testimony: In 2007, Microsoft employee Ronald Alepin gave sworn expert testimony for the plaintiffs in Comes v. Microsoft in which he cited internal Microsoft emails to justify the claim that the company intentionally employed this practice.[24]
• Email Protocols: Microsoft supported POP3, IMAP, and SMTP email protocols in their Microsoft Outlook email client. At the same time, they developed their own email protocol, MAPI, which has since been documented but is largely unused by third parties. Microsoft has announced that they will end support for basic authentication access to Exchange Online API's for Office 365 customers, which disables most use of IMAP or POP3 and requires significant upgrades to applications in order to continue to use those protocols;[25] some customers have responded by simply shutting off older protocols.[26]
• Unix/Linux: Microsoft included a bare-minimum POSIX layer from the beginning of NT, later replaced with Windows Services for UNIX, a more full-featured UNIX based on Interix with various unique features that were not portable to other *nixes. Windows Subsystem for Linux replaced it in 2018, a heavily modified Linux compatibility layer that caused fears of EEE.[27] The current WSL2 has moved away from reimplementing Linux to virtualizing an actual Linux kernel and allowing full distro installs, beginning with Ubuntu.[28]

An older variant of the phrase is "embrace, extend then innovate" in J Allard's 1994 memo "Windows: The Next Killer Application on the Internet"[29] to Paul Maritz and other executives at Microsoft. The memo starts with a background on the Internet in general, and then proposes a strategy on how to turn Windows into the next "killer app" for the Internet:

In order to build the necessary respect and win the mindshare of the Internet community, I recommend a recipe not unlike the one we've used with our TCP/IP efforts: embrace, extend, then innovate. Phase 1 (Embrace): all participants need to establish a solid understanding of the infostructure and the community—determine the needs and the trends of the user base. Only then can we effectively enable Microsoft system products to be great Internet systems. Phase 2 (Extend): establish relationships with the appropriate organizations and corporations with goals similar to ours. Offer well-integrated tools and services compatible with established and popular standards that have been developed in the Internet community. Phase 3 (Innovate): move into a leadership role with new Internet standards as appropriate, enable standard off-the-shelf titles with Internet awareness. Change the rules: Windows become the next-generation Internet tool of the future.

— J Allard, Windows: The Next Killer Application on the Internet

During the browser wars, other companies besides Microsoft introduced proprietary, non–standards-compliant extensions. For example, in 1995, Netscape implemented the "font" tag, among other HTML extensions, without seeking review from a standards body. With the rise of Internet Explorer, the two companies became locked in a dead heat to out-implement each other with non–standards-compliant features. In 2004, to prevent a repeat of the "browser wars", and the resulting morass of conflicting standards, the browser vendors Apple Inc. (Safari), Mozilla Foundation (Firefox), and Opera Software (Opera browser) formed the Web Hypertext Application Technology Working Group (WHATWG) to create open standards to complement those of the World Wide Web Consortium.[30] Microsoft refused to join, citing the group's lack of a patent policy as the reason.[31]

• Criticism of Microsoft
• Halloween documents
• Microsoft and open source
• Network effect
• Path dependence
• Vendor lock-in
• 32-bit vs 64-bit
• AARD code

• Report on Microsoft documents relating to Office and IE Embrace, extend and extinguish