태그

So I’d say a library is just that, “a library”. It is a collection of objects/functions/methods (depending on your language) and your application “links” against it and thus can use the objects/functions/methods. It is basically a file containing re-usable code that can usually be shared among multiple applications (you don’t have to write the same code over and over again).

A framework can be everything you use in application development. It can be a library, a collection of many libraries, a collection of scripts, or any piece of software you need to create your application. Framework is just a very vague term.

via terminology – What is the difference between a framework and a library? – Stack Overflow.

/*Therefore, the API is certainly border concept than just library*/

 

프레임워크는 라이브러리와 달리 애플리케이션의 틀과 구조를 결정할 뿐 아니라, 그 위에 개발된 개발자의 코드를 제어한다. 프레임워크는 구체적이며 확장 가능한 기반 코드를 가지고 있으며, 설계자가 의도하는 여러 디자인 패턴의 집합으로 구성되어 있다.

via 까먹지말자! : 프레임워크(Framework)가 뭔가요?.

 

Advertisements