Topics /

History & Retro Computing

The most popular blog posts about history & retro computing on Hacker News. 390 posts.

2022
130

The First Lisp Compiler

This page examines the earliest surviving Lisp compiler, written by Timothy Hart and Michael Levin around 1961. To avoid repetition of phrases like “the compiler”, we will use the abbreviation “ HLC ” (for “Hart–Levin Compiler”) to refer to it. The HLC was introduced in M.I.T. AIM -039 and documented more fully in the…

131

Why wasn't the steam engine invented earlier? Part II

As I noted in Part I, the general idea of using heat and steam for mechanical work had a long and continuous history back to ancient times. But when we talk of the breakthrough “steam engine” in the eighteenth-century sense, we don’t mean a machine that exploits steam’s expansive, or pushing force. We actually mean a…

139

Win16 Retro Development

Several months ago I had a go at producing a high resolution 256-color driver for Windows 3.1. The effort was successful but is not yet complete. Along the way I re-learned many things I had forgotten, and learned several new ones. This blog entry is based on notes I made during development.

143

3Hz Computer, Hold the Transistors

I’m not really one to brag publicly about expensive toys, but a few weeks ago I managed to get one that’s really something special. It is a Curta Type II , a mechanical digital 1 calculator manufactured in Liechtenstein between the 50s and 70s, before solid-state calculators killed them and the likes of slide-rules.

145

Retro Compaq LTE Laptop Powered by Raspberry Pi

A while ago a came across an old Compaq LTE 286 laptop. When they were first released around 1989, these PCs were somewhat groundbreaking because they were the first to be compact enough to resemble the “notebook” form factor that we take for granted today. Unfortunately this particular unit was pretty much beyond…

148

My story on “worse is better” (2018)

“ The Rise of Worse is Better ” is a famous essay in the software industry. It says that lazily-looking code that does not provide a consistent interface is sometimes actually better than neatly layered, consistent one. I think I've experienced this paradoxical situation, so I'd like to share that story.