Retrologic Systems Retrologic Systems Retrologic Systems
Online Jargon File
  RetroGuard  |  RetroCapture  |  Contracting  |  Site Map  |  Contact

forked - The Jargon File

0 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Jargon On Your Website    Random Entry (Alt-R)RSS Feed - Random Jargon
forked: adj.,vi.

1. [common after 1997, esp. in the Linux community] An open-source software project is said to have forked or be forked when the project group fissions into two or more parts pursuing separate lines of development (or, less commonly, when a third party unconnected to the project group begins its own line of development). Forking is considered a Bad Thing — not merely because it implies a lot of wasted effort in the future, but because forks tend to be accompanied by a great deal of strife and acrimony between the successor groups over issues of legitimacy, succession, and design direction. There is serious social pressure against forking. As a result, major forks (such as the Gnu-Emacs/XEmacs split, the fissionings of the 386BSD group into three daughter projects, and the short-lived GCC/EGCS split) are rare enough that they are remembered individually in hacker folklore.

2. [Unix; uncommon; prob.: influenced by a mainstream expletive] Terminally slow, or dead. Originated when one system was slowed to a snail's pace by an inadvertent fork bomb.


 
 Copyright © 1998-2006 Retrologic Systems. retroguard | retrocapture | contracting | site map | contact
 All rights reserved. site terms | privacy policy