this post was submitted on 04 Mar 2025
47 points (100.0% liked)

Programming

18675 readers
108 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
47
What is the difference between an API, a Library, a Package, and a Framework? (sh.itjust.works)
submitted 5 days ago by [email protected] to c/programming
17 comments fedilink hide all child comments
 

I have some familiarity with C++, and concepts like compiling and linking static and dynamic libraries, which is what I understand as collections of code that simplify doing certain things.

But then I get confused in certain cases, for example, why is OpenGL considered an API? Why is it necessary to use other libraries like GLAD, freeGLUT or GLFW to interface with OpenGL?

And then other languages have this thing called package managers, like pip, node, cargo, and vcpkg for c/c++, where you install these packages that get used like libraries? What's the difference?

Finally the ones I understand the least of are frameworks. I keep hearing the concept of frameworks like Angular for js and a lot of stuff that's too alien for me because I'm still unfamiliar with web development.

So for example, I'm using the raylib library for a small game project I have. I link the .lib or .dll file to my executable file so I know I'm unambiguously using a library. How come there's also Cocos2dx which is a framework? What's the distinction?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 4 days ago

They’re overlapping concepts, and can be used interchangeably. Sometimes a library can be all of them at the same time. In simple terms:

  • API is the interface to the library.
  • Library is code that is shared.
  • Package is how it’s distributed.
  • Framework is the methodology the library is used.

Not all APIs are libraries. For example, all websites have some interface to interact with them. A website is not a library.

Not all libraries are packages. A library don’t need to be distributed through a package manager.

Framework is a bit blurry where the line is drawn. I think if the library is used in such way that your entire program revolves around it, then it’s a framework. If you’re just using it a handful of times, then it’s not a framework.

React and Angular are frameworks in this regard. If you use them, then your entire programming is revolving around them. Any decision made is in regard to these frameworks.

I would say OpenGL is API, library and framework. Maybe also package depending on how it’s distributed.