Уровень 0 · материалов: 5
В кластер входят документы, описывающие конкретные технические ошибки или недостатки проектирования, приведшие к системным сбоям или долгосрочным проблемам в ПО, и не входят документы о пользовательском опыте установки ОС или истории развития системных вызовов.
Общие признаки: технические ошибки, неудачные проектные решения, системные сбои, непредвиденные последствия разработки
Группа выше: Причины программных ошибок
Смысл: A small, lazy optimization in early Unix code created the 'hidden file' convention by mistake, demonstrating how minor shortcuts in software architecture can lead to decades of systemic inefficiency and unintended behavioral standards.
The convention of hidden files in Unix started as a lazy coding shortcut that evolved into a problematic 'feature', warning developers against the long-term costs of cutting corners.
Смысл: A small typo (a space) in the Bumblebee driver installer led to the accidental deletion of the /usr directory, demonstrating how minor scripting errors can cause catastrophic system failure in Linux.
A typo in the Bumblebee 1.4.31 installer accidentally deleted users' /usr folders, leading to a public apology and a quick fix.
Смысл: The text explores three historically disastrous programming features—VB's silent error suppression, Windows Forms' DoEvents, and COBOL's dynamic GOTO—to illustrate how bad design choices can lead to maintainability nightmares and unpredictable software behavior.
A critical look at three legacy programming features—VB's silent error handling, Windows Forms' DoEvents, and COBOL's dynamic GOTO—that created unpredictable and unmaintainable code.
Смысл: The main idea is that a specific technical limitation in IBM hardware led MS-DOS developers to use a human-based benchmark (the physical speed of swapping a disk) to determine the optimal timeout for the floppy disk read cache.
MS-DOS set its floppy disk read buffer to two seconds because that was the fastest time developers could physically swap a disk during a timed test.
Смысл: The text illustrates how poorly written third-party software can cause systemic failures in unrelated applications by monopolizing shared system resources, specifically OpenGL objects in this case.
A programmer is baffled when a UPS seems to crash his software, only to discover that the bundled UPS monitoring utility was leaking OpenGL resources until the system was exhausted.