Bootloader
/ˈbuːt.loʊ.dər/ · Noun · Development · Origin: 1975
Definitions
A small program that runs first when a device powers on, responsible for initializing hardware and loading the main operating system or application firmware into memory.
In plain English: The first tiny program that runs when you turn on a device. Its only job is to get everything ready and then hand off to the real operating system, like an opening act warming up the stage.
Example: "We added a dual-bank bootloader so the device can fall back to the previous firmware if an OTA update fails mid-flash."
Origin Story
The tiny program that has the impossible job of starting from nothing
The **bootloader** solves a chicken-and-egg problem: to load an operating system from disk, you need a program to read the disk, but that program itself needs to be loaded somehow. The term comes from the phrase 'pulling yourself up by your bootstraps.'
Early computers were bootstrapped manually -- operators toggled switches to enter a small program that could load a larger program. The IBM 701 (1952) had a 'load' button that read 36 words from a punch card, just enough to bootstrap the rest of the system.
Modern bootloaders like GRUB, systemd-boot, and U-Boot are sophisticated programs in their own right. UEFI Secure Boot adds cryptographic verification to prevent bootkits. But the core problem remains the same: start with nothing, get to something.
Coined by: Computing community (from 'bootstrap' idiom)
Context: 1950s mainframe era
Fun fact: The phrase 'pull yourself up by your bootstraps' was originally meant as an absurdity -- it's physically impossible. Computer scientists adopted it anyway because bootstrapping a computer from nothing feels equally impossible, yet somehow works.