Discussion of the ship's scuttling procedure, and the odd 'destruction keyboard' layout in particular I found totally fascinating. I was actually quite surprised at the level of detail the set designers went to with this movie.
If you are not a typography fan - do yourself a favour and push through the initial part of the article and wait for the bits where the author zooms in on particular screenshots to explore tiny details like the ship/company logo on cat dishes and beer cans etc.
As opposed to Windows, which did not at the time.
He wasn't claiming he invented decent fonts on a computer.
> As opposed to Windows, which did not at the time.
And to a point, this is still true. It's surprisingly hard to get good text rendering in terminal emulators on Windows and Linux. I still have to settle for "good enough" rather than the "stellar" I can get on my OS X machine.
Also I guess it depends on what kind of programming... frontend devs probably care more about it than embedded devs.
When I write an article saying I'm doing something better in code I need to demonstrate it empirically.
Maybe that's not a reasonable way to read a design article though.
Someone said they don't like reading about typography in general. I seconded and explained why.
Airport signage is another pretty good example. I always look for the little man/woman symbols with an arrow pointing to the restrooms. I've missed signs that actually say "Restrooms ->" because there's so much visual clutter in airports. And i'm usually tired and a bit stressed out about making my connection.
Perhaps it is pseudoscience. In this context, I'd be willing to agree it's all just learned conventions. I'd argue, studying those conventions, and exploiting them is more than nothing though.
You should never remember a good sign. it's noticed, used and forgotten. You will always remember a bad sign.