Hrmn. The various analogies are perhaps a bit fluffy, and the email and drag-and-drop examples are perhaps not particularly convincing. But man, I wish Lampor

Hrmn. The various analogies are perhaps a bit fluffy, and the email and drag-and-drop examples are perhaps not particularly convincing. But man, I wish Lamport's call for our industry to think more logically and design programs more mathematically would gain more traction. These little inconsistencies add up to create horrible messes. This is true everywhere from our programs to our languages to the core abstractions and APIs that we work with. Some examples off the top of my head: - "Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems" (https://www.dwheeler.com/essays/fixing-unix-linux-filenames.html https://www.dwheeler.com/essays/fixing-unix-linux-filenames....) - "Parsing JSON is a Minefield" (http://seriot.ch/parsing_json.php http://seriot.ch/parsing_json.php) - "Into the Depths of C: Elaborating the De Facto Standards" (http://www.cl.cam.ac.uk/~pes20/cerberus/pldi16.pdf http://www.cl.cam.ac.uk/~pes20/cerberus/pldi16.pdf) - "PHP: a fractal of bad design" (https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/)