computers/why-your-computer-forgets-unsaved-work-when-the-power-dies.md
Why your computer forgets unsaved work when the power dies
Your computer has two kinds of memory. Storage (the SSD or hard drive) is a big filing cabinet that keeps files with the power off. RAM is a small, very fast desk that holds whatever is open right now, and forgets it all the instant power stops.
Opening a file copies it from storage into RAM; saving copies it back. That's why a power cut leaves you with the last saved version. Try a desk-and-cabinet simulator with a pull-the-plug button, and see how much slower storage really is when one RAM access takes a second.
$ ls computers/
see all →
computers/endianness-why-the-bytes-of-a-number-can-be-stored-backwards.md
Endianness: why the bytes of a number can be stored backwards
Store the number 0x12345678 in memory and you might expect the bytes in the order 12 34 56 78. Most laptops and phones store them as 78 56…
computers/deadlock-how-two-programs-can-wait-for-each-other-forever.md
Deadlock: how two programs can wait for each other forever
Two threads each hold one lock and wait for the other's. Neither can move, and the program just freezes without an error. This is a…
computers/virtual-memory-why-two-programs-can-use-the-same-address-without-clash.md
Virtual memory: why two programs can use the same address without clashing
Two programs can both use "address 4096" without ever touching each other's data. The trick is that the addresses a program sees are…
computers/fetch-decode-execute-the-three-beat-loop-every-cpu-repeats-billions-of.md
Fetch, decode, execute: the three-beat loop every CPU repeats billions of times a second
A processor looks clever, but at its core it repeats one small loop billions of times a second: fetch an instruction, decode what it asks…
computers/the-call-stack-why-a-function-that-never-stops-crashes-your-program.md
The call stack: why a function that never stops crashes your program
Every time a function is called, the computer puts a small block of memory called a frame on top of a call stack, and removes it when the…
computers/floating-point-why-0-1-0-2-is-not-exactly-0-3.md
Floating point: why 0.1 + 0.2 is not exactly 0.3
Type `0.1 + 0.2` into JavaScript or Python and you get `0.30000000000000004`. It is not a bug, and it is not your mistake. Computers store…