Bleeding edge technology

"Bleeding edge" redirects here. It is not to be confused with Bleeding Edge the novel, leading edge (disambiguation), or cutting edge (disambiguation), state of the art (disambiguation).

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.[1][2] 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.[3] 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.[4]

By its nature, a proportion of bleeding edge technology will make it into the mainstream. For example, electronic mail (email) was once considered to be bleeding edge.[5]

Criteria

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:

Costs and benefits

The rewards for successful early adoption of new technologies can be great in terms of established a comparative advantage in otherwise competitive markets;[2] 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.[6]

See also

Notes

  1. "bleeding edge. (n.d.)". Dictionary.com Unabridged. Random House. Retrieved 12 September 2008.
  2. 1 2 3 4 Effy Oz (23 January 2008). Management Information Systems. Cengage Learning. p. 65. ISBN 978-1-4239-0178-5. Retrieved 9 November 2010.
  3. 1 2 3 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.
  4. Hayes, Thomas C. (21 March 1983). "Hope at Storage Technology". The New York Times. Retrieved 10 September 2013.
  5. Infosystems. Hitchcock Pub. Co. 1977. p. 64. Retrieved 14 December 2011.
  6. Rikishi, Niramiai (December 2000). "Selling in the Bazaar: How Open Source Manages Code". AAUGN (AUUG, Inc.): 41. Retrieved 9 November 2010.

External links

This article is issued from Wikipedia - version of the Tuesday, March 15, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.