Related:

• bug-compatible adj. [common] Said of a design or revision that has been badly compromised by a requirement to be compatible with fossils or misfeatures in other programs or (esp.
  ) previous releases of itself. "MS-DOS 2.0 used \ as a path separator to be bug-compatible with some cretin's choice of / as an option character in 1....
• bug-for-bug compatible: n. Same as {bug-compatible}, with the additional implication that much tedious effort went into ensuring that each (known) bug was replicated.
  -- The AI Hackers Dictionary...
• fossil: n. 1. In software, a misfeature that becomes understandable only in historical context, as a remnant of times past retained so as not to break compatibility.
  Example: the retention of octal as default base for string escapes in {C}, in spite of the better match of hexadecimal to ASCII and modern byte-addressable architectures....
• hysterical reasons: (also `hysterical raisins') n. A variant on the stock phrase "for historical reaso
  indicating specifically that something must be done in some stupid way for backwards compatibility, and moreover that the feature it must be compatible with was the result of a bad design in the first place....
• zip: [primarily MS-DOS] vt. To create a compressed archive from a group of files using PKWare's PKZIP or a compatible archiver.
  Its use is spreading now that portable implementations of the algorithm have been written....
• estriction: n. A {bug} or design error that limits a program's capabilities, and which is sufficiently egregious that nobody can quite work up enough nerve to describe it as a {feature}.
  Often used (esp. by {marketroid} types) to make it sound as though some crippling bogosity had been intended by the designers all along, or was forced upon them by arcane technical constraints of a nature no mere user could possibly comprehend (these claims are almost invariably false)....
• well-behaved: adj. 1. [primarily {{MS-DOS}}] Said of software conforming to system interface guidelines and standards.
  Well-behaved software uses the operating system to do chores such as keyboard input, allocating memory and drawing graphics....
• Nothing is 100% certain, bug free or IBM compatible.
• fossil n. 1. In software, a misfeature that becomes understandable only in historical context, as a remnant of times past retained so as not to break compatibility.
  Example: the retention of octal as default base for string escapes in C, in spite of the better match of hexadecimal to ASCII and modern byte-addressable architectures....