Bleeding edge technology
Bleeding edge technology is a category of technologies so new that they could have a high risk of being unreliable and lead adopters to incur greater expense in order to make use of them. The term bleeding edge was formed as an allusion to the similar terms "leading edge" and "cutting edge". It tends to imply even greater advancement, albeit at an increased risk because of the unreliability of the software or hardware. The first documented example of this term being used dates to early 1983, when an unnamed banking executive was quoted to have used it in reference to Storage Technology Corporation.
A technology may be considered bleeding edge where it contains a degree of risk, or, more generally, there is a significant downside to early adoption, such as:
- Lack of consensus – competing ways of doing new things exist and there is little to no indication in which direction the market will go. By its very nature, consumers and firms will be unfamiliar with the product and its relationship to existing technologies, leading to rapid changes in what is considered best practice as more becomes known about the technology's qualities.
- Lack of testing – The technology may be unreliable, or simply untested.
- Industry resistance to change – trade journals and industry leaders have spoken against a new technology or product but some organizations are trying to implement it anyway because they are convinced it is technically superior.
Costs and benefits
The rewards for successful early adoption of new technologies can be great in terms of establishing a comparative advantage in otherwise competitive markets; unfortunately, the penalties for "betting on the wrong horse" (e.g. in a format war) or choosing the wrong product are equally large. Whenever an organization decides to take a chance on bleeding edge technology there is a chance that they will be stuck with a white elephant or worse.
Bleeding edge computer software, especially open source software, is especially common. Indeed, it is usual practice for open-source developers to release new, bleeding edge, versions of their software fairly frequently, sometimes in a rather unpolished state to allow others to review, test, and, in many cases, contribute to it (beta testing). Therefore, users who want features that have not been implemented in older, more stable releases of the software are able to choose the bleeding-edge version. In such cases, the user is willing to sacrifice stability, reliability, or ease of use for the sake of increased functionality.
- "bleeding edge. (n.d.)". Dictionary.com Unabridged. Random House. Retrieved 12 September 2008.
- Effy Oz (23 January 2008). Management Information Systems. Cengage Learning. p. 65. ISBN 978-1-4239-0178-5. Retrieved 9 November 2010.
- Ingo Schommer; Steven Broschart (7 January 2010). SilverStripe: The Complete Guide to CMS Development. John Wiley & Sons. p. 22. ISBN 978-0-470-68270-8. Retrieved 14 December 2011.
- Hayes, Thomas C. (21 March 1983). "Hope at Storage Technology". The New York Times. Retrieved 10 September 2013.
- Infosystems. Hitchcock Pub. Co. 1977. p. 64. Retrieved 14 December 2011.
- Rikishi, Niramiai (December 2000). "Selling in the Bazaar: How Open Source Manages Code". AAUGN. AUUG, Inc.: 41. Retrieved 9 November 2010.
- The dictionary definition of bleeding edge at Wiktionary