Wednesday, July 27, 2016

Why is it called a "software library"?

I have been picking up programming again as part of work, and making use of a lot of software libraries. Compared to the good old days, there are a lot more libraries now. Back in the good old days, if you needed to do something, chances are you have to come up with the code yourself. Now, a search on Google should likely give you the name of a library that does what you need.

That got me thinking... why is it called a "library" in the first place?

This is something I found.
What's the origin of using the term "library" for software?

If the term "library" really came from back in 1951... then I think it is most likely because back then, programs were probably stored on punch cards. So frequently used subroutines are probably stored and catalogued like books in a library to make them easy to find. So in a way, just like you go to a library to borrow a book, you go to a software library to borrow a subroutine.

Well, another way to look at it, from my own personal (twisted and unofficial) point of view, is that back in the good old days, when the Internet is limited to research institutes and universities and military establishments, people share commonly used subroutines/functions by writing books. Programmers then go to libraries (the physical ones with books) to search for books with subroutines/functions, borrow these books, and use the code in there.

So one goes to a library to borrow books on programming which comes with code inside that can be reused.

And so code that can be reused is thus known as a "library".

And that's my own (unofficial, and probably untrue) view on the origin of the term "library" for software.

;)

No comments: