Backward compatibility is a property of a system, product, or technology that allows for interoperability with an older legacy system, or with input designed for such a system, especially in telecommunications and computing. Backward compatibility is sometimes also called downward compatibility.
Modifying a system in a way that does not allow backward compatibility is sometimes called "breaking" backward compatibility.
In programming jargon, the concept is sometimes referred to as hysterical reasons or hysterical raisins, homophones for "historical reasons".
There are several incentives for a company to implement backward compatibility. Backward compatibility can be used to preserve older software that would have otherwise been lost when a manufacturer decides to stop supporting older hardware. Classic video games are a common example used when discussing the value of supporting older software. The cultural impact of video games is a large part of their continued success, and some believe ignoring backward compatibility would cause these titles to disappear. Backward compatibility also acts as an additional selling point for new hardware, as an existing player base can more affordably upgrade to subsequent generations of a console. This also helps to make up for a lack of content in the early launch of new systems, as users can pull from the previous console's large library of games while developers slowly transition to the new hardware.
One example of this is the Sony PlayStation 2 (PS2) which was backward compatible with games for its predecessor PlayStation (PS1). While the selection of PS2 games available at launch was small, sales of the console were nonetheless strong in 2000-2001 thanks to the large library of games for the preceding PS1. This bought time for the PS2 to grow a large installed base and developers to release more quality PS2 games for the crucial 2001 holiday season.
Additionally, and despite not being included at launch, Microsoft slowly incorporated backward compatibility for select titles on the Xbox One several years into its product life cycle. Players have racked up over a billion hours with backward compatible games, and it is rumored that next generation console like the PlayStation 5 will also support this feature. A large part of the success and implementation of this feature is that the hardware within newer generation consoles is both powerful and similar enough to legacy systems that older titles can be broken down and re-configured to run on the Xbox One. The backward compatibility program not only supports the previous generation Xbox 360, but also titles from the original Xbox system. Some titles are even given slight visual improvements and additional levels at no cost to the user. This program has proven incredibly popular with Xbox players and goes against the recent trend of studio made remasters of classic titles, creating what some believe to be an important shift in console maker's strategies.
The literal costs of supporting old software is considered a large drawback to the usage of backward compatibility. The associated costs of backward compatibility are a higher bill of materials if hardware is required to support the legacy systems; increased complexity of the product that may lead to longer time to market, technological hindrances, and slowing innovation; and increased expectations from users in terms of compatibility. Because of this, several gaming consoles chose to phase out backward compatibility toward the end of the console generation in order to reduce cost and briefly re-invigorate sales before the arrival of newer hardware.
A notable example is the Sony PlayStation 3, as the first PS3 iteration was expensive to manufacture in part due to including the Emotion Engine from the preceding PS2 in order to run PS2 games, since the PS3 architecture was completely different from the PS2. Subsequent PS3 hardware revisions have eliminated the Emotion Engine as it saved production costs while removing the ability to run PS2 titles, as Sony found out that backward compatibility was not a major selling point for the PS3. in contrast to the PS2. The PS3's chief competitor, the Microsoft Xbox 360, took a different approach to backward compatibility by using software emulation in order to run games from the first Xbox, rather than including legacy hardware from the original Xbox which was quite different from the Xbox 360, however Microsoft stopped releasing emulation profiles after 2007.
However, with the current decline in physical game sales and the rise of digital storefronts and downloads, some believe backwards compatibility will soon be as obsolete as the phased-out consoles it supports. Many game studios are re-mastering and re-releasing their most popular titles by improving the quality of graphics and adding new content. These remasters have found success by appealing both to nostalgic players who remember enjoying the original versions when they were younger, and to newcomers who may not have had the original system it was released on. For most consumers, digital remasters are more appealing than hanging on to bulky cartridges and obsolete hardware. For the manufacturers of consoles, digital re-releases of classic titles are a large benefit. It not only removes the financial drawbacks of supporting older hardware, but also shifts all of the costs of updating software to the developers. The manufacturer gets a new addition to their system with strong name recognition, and the studio does not have to completely develop a game from the ground up.
A simple example of both backward and forward compatibility is the introduction of FM radio in stereo. FM radio was initially mono, with only one audio channel represented by one signal. With the introduction of two-channel stereo FM radio, many listeners had only mono FM receivers. Forward compatibility for mono receivers with stereo signals was achieved through sending the sum of both left and right audio channels in one signal and the difference in another signal. That allows mono FM receivers to receive and decode the sum signal while ignoring the difference signal, which is necessary only for separating the audio channels. Stereo FM receivers can receive a mono signal and decode it without the need for a second signal, and they can separate a sum signal to left and right channels if both sum and difference signals are received. Without the requirement for backward compatibility, a simpler method could have been chosen.
Full backward compatibility is particularly important in computer instruction set architectures, one of the most successful being the x86 family of microprocessors. Their full backward compatibility spans back to the 16-bit Intel 8086/8088 processors introduced in 1978. (The 8086/8088, in turn, were designed with easy machine-translatability of programs written for its predecessor in mind, although they were not instruction-set compatible with the 8-bit Intel 8080 processor as of 1974. The Zilog Z80, however, was fully backwards compatible with the Intel 8080.) Fully backwards compatible processors can process the same binary executable software instructions as their predecessors, allowing the use of a newer processor without having to acquire new applications or operating systems. Similarly, the success of the Wi-Fi digital communication standard is attributed to its broad forward and backward compatibility; it became more popular than other standards that were not backward compatible.
Compiler backward compatibility may refer to the ability of a compiler of a newer version of the language to accept programs or data that worked under the previous version.
- Bug compatibility, backward compatibility that maintains known flaws
- Compatibility mode
- Computer compatibility
- Downgrade attack
- Flag day (computing)
- Legacy mode
- List of backward compatible games for Xbox One
- List of Xbox games compatible with Xbox 360
- Software regression
- Vendor lock-in
- J.K. Petersen (2002), The Telecommunications Illustrated Dictionary (Second ed.), CRC Press, ISBN 9781420040678
- Paul Belleflamme; Martin Peitz (2010), "Strategies in standard wars", Industrial Organization: Markets and Strategies, Cambridge University Press, ISBN 9780521862998
- Jeffrey Zeldman (2006). Designing with Web Standards. Peachpit Press. pp. 15–16. ISBN 0-321-38555-1.
- "hysterical reasons". FOLDOC. Retrieved 2019-06-25.
- Raymond, Eric S. (29 Dec 2003). "hysterical reasons". catb.org. Retrieved 2019-06-25.
- Kumari, Warren (2017-07-05). "RFC 8279: Multicast Using Bit Index Explicit Replication". datatracker.ietf.org. IETF. Retrieved 2019-06-25.
Warren Kumari (Google): "discuss comment below for hysterical raisins"
- "Backwards Compatibility is the Only Way Forward". PopMatters. 2015-04-10. Retrieved 2019-11-05.
- "Understanding backwards compatibility and how it benefits gamers". Tech Magazine. 2018-08-14. Retrieved 2019-11-05.
- "Remasters aren't needed if the PS5 is completely backward compatible". Android Central. 2019-09-24. Retrieved 2019-11-10.
- Leadbetter, Richard (2017-12-09). "Xbox One backwards compatibility: how does it actually work?". Eurogamer. Retrieved 2019-11-10.
- Stein, Scott. "Game consoles and the death of backward-compatibility: Why we don't care". CNET. Retrieved 2019-11-05.
- tweet_btn(), Tony Smith 16 Nov 2006 at 12:00. "Sony PS3 'costs at least $805-840' to make". www.theregister.co.uk. Retrieved 2019-03-08.
- Arendt, Susan (2007-02-26). "Sony Confirms Backwards Compatibility Dumped to Lower Costs". Wired. ISSN 1059-1028. Retrieved 2019-03-08.
- "MS Engineer Speaks on Xbox 360 Backward Compatibility - Xbox". web.archive.org. 2013-04-01. Retrieved 2019-03-08.
- Winder, Steve; Carr, Joseph (2002), Newnes Radio and RF Engineering Pocket Book (3 ed.), Newnes, pp. 121–123, ISBN 9780080497471
- Naresh Jotwani (2009), Computer System Organization, Tata McGraw-Hill Education, pp. 320–324, ISBN 9781259081217
- Perahia, Eldad; Stacey, Robert (2013), "Foreword", Next Generation Wireless LANs: 802.11n and 802.11ac, Cambridge University Press, ISBN 9781107016767
- Kay, Michael (2004). XSLT 2.0 Programmer's Reference. Wiley. ISBN 0-7645-6909-0.
- Bos, Bert (2003). "Backwards Compatibility". What is a Good Standard?. Retrieved July 12, 2016.