Frameworks and Libraries
Don’t Call Us, We’ll Call You
Library
- Performs a specific operation
- Re-usable code or a collection of routines
- Easier to swap out if one library doesn’t work, swapping a Framework could be like starting a project over
Framework
- The skeleton that helps structure the meat
- Provides your code with a frame (saves time)
- Helps add consistency to the project
- Can contain a library
Don’t Call us:
Framework: You don’t ask the framework to do anything, it waits for your code and then runs it through it’s skeleton and prints it to the page.
We’ll Call You:
Library: You ask the library to help you do a specific task by calling it.
Reading Material
- (A few) Framework Comparisons https://www.airpair.com/js/javascript-framework-comparison
- 2 Libraries and a Framework for 2015 http://www.sitepoint.com/3-javascript-libraries-keep-eye-2015/
- Very simple example of Angular http://codepen.io/martinwolf/pen/LmpeH
Links to Frameworks & Libraries discussed at the Meetup
- Node (framework): https://nodejs.org/
- NodeSchool (lots ‘o tutorials): http://nodeschool.io/
- React (library for UI): http://facebook.github.io/react/index.html
- Firebase (data storage & backend support): https://www.firebase.com/
- Vue (Library): http://vuejs.org/
- D3 (Data Visualization): http://d3js.org/
- C3 (Data Visualization): http://c3js.org/
- Meteor (Framework): https://www.meteor.com/install
- Mean (Full Stack JS - Mongo DB, Express, Angular, Node): http://mean.io/#!/
- Yeoman (Kickstart Projects quickly): http://yeoman.io/