Most people who see "API" today only think "it's a web app I send a request to, and I pass some arguments and set some headers, then check some settings from the returned headers, then parse some returned data."

But "API" means "Application Programming Interface". It was originally for application programs, which were... programs with user interfaces! It comes from the 1940's originally, and wasn't referred to for much else until 1990. APIs have existed for over 80 years. Books and papers have been published on the subject that are older than many of the people reading this text right now.

What might've those older APIs been like? What were they working with? What was their purpose? How did those programmers solve their problems? How might that be relevant to you?

▲

spacechild1 3 days ago | parent | next [-]

You are talking in past tense, but there are still many non-web APIs. Every software library has an API. I still find it incredibly annoying that the web folks have hijacked the term "API" as a short hand for "web API".

▲

stronglikedan 2 days ago | parent [-]

> the web folks have hijacked the term "API" as a short hand for "web API".

I don't see it. API is too vague to mean one type of API, whether it's one from before the web, or a web API. As soon as there was more than one type of API, the term API became incomplete without a qualifier. Nothing was hijacked, and your sentence includes an incomplete term.

	▲	spacechild1 2 days ago \| parent [-]
		Web devs absolutely do use "API" as a synonym for "web API". I mean, the title of this very submission is "Everything I know about good API design". One could naively expect an article about API design in general, but it's only about web APIs.

▲

1718627440 2 days ago | parent | prev | next [-]

You are talking as if it were a thing of a past. Yet I am 20 and when I read API, only ever think of it as in API/ABI. I don't think a protocol endpoint is an API.

▲

fanf2 2 days ago | parent | prev [-]

> It comes from the 1940's originally

Really?! That’s amazingly early. There were barely even subroutine libraries at that time. I’d love to see an example of "Application Programming Interface" from that time.

(I don’t remember seeing the term until Microsoft started using it when talking about Windows in the 1990s; before then it was things like library functions or supervisor calls - but I didn’t have much experience at that point so I was probably missing some of the more collar-and-tie programmer lingo.)