Libraries & Frameworks Overview
- Libraries & Frameworks
- Top 20 Python AI and Machine Learning Open Source Projects
- Comparison of deep learning software | Wikipedia
- Modern AI Stack & AI as a Service Consumption Models
- 39 Machine Learning Libraries for Spark
- Top Deep Learning Tools | Josh Poduska - RTInsights
- Git - GitHub and GitLab
The key difference between a library and a framework is "Inversion of Control". When you call a method from a library, you are in control. But with a framework, the control is inverted: the framework calls you.
- Library - a collection of code or class definitions. The reason behind is simply code reuse, i.e. get the code that has already been written by other developers. The classes and methods normally define specific operations in a domain specific area. For example, there are some libraries of mathematics which can let developer just call the function without redo the implementation of how an algorithm works.
- Framework - all the control flow is already there, and there's a bunch of predefined white spots that you should fill out with your code. A framework is normally more complex. It defines a skeleton where the application defines its own features to fill out the skeleton. In this way, your code will be called by the framework when appropriately. The benefit is that developers do not need to worry about if a design is good or not, but just about implementing domain specific functions.