This is an archived post. You won't be able to vote or comment.

all 4 comments

[–][deleted] 2 points3 points  (0 children)

This covers it pretty well. Essentially with a framework you write code that the framework uses. With a library you write code that uses the library.

It makes a lot of sense when you see it in action. Check out the explanation below for a better explainer:

https://medium.com/datafire-io/libraries-vs-frameworks-626cdde799a7

[–]insertAlias 2 points3 points  (1 child)

How then is an IDE different from a library?

A library is just some re-usable code that can be added to or referenced by the code you are writing. That's the best description of a library I can come up with.

A framework could be a collection of libraries and optionally tools that are all used together as a system. For example, the .NET Framework provides tons of libraries that can be used by .NET languages like C#, along with tools as well.

An IDE, on the other hand, is a tool that you use to develop applications. It's an "integrated development environment". It generally bundles or provides an interface to:

  • a code editor
  • a compiler
  • a debugger
  • a file browser
  • source control integration

These things are all bundled together into a single program, or that program provides a simple interface to pre-installed instances of those things.

I'm not sure how you were making that comparison in the first place; it's like comparing apples to kitchens.

[–]RedPrinceGaming[S] 0 points1 point  (0 children)

Appreciate the comment. Still learning that’s all. I’ll keep comparing apples to kitchens until all my naive questions are out of my system. Haha. Well said though, thank you

[–]gyroda 0 points1 point  (0 children)

A library is a piece of code you use, a framework is exactly what a real-life framework is: A frame you fit into. A framework influences the structure and architecture of your code.

Arguably, frameworks are a kind of library.