a supporting structure around which something can be built
– Definition by Cambridge Dictionary
Originally, frameworks were meant to address this problem by providing developers with more control over how their applications would run.
This was achieved in a number of ways including putting all code that is meant for re-use into a self-contained entity known as framework.
This idea of re-usable frameworks ultimately turned into libraries.
Depending on who you ask, the line between libraries and frameworks may seem blurred, but there are some key differences that need to be addressed.
We will dive into this aspect in a bit.
Let’s start with one important question.
So you are rightfully thinking what’s all the fuzz about?
Let’s start at the beginning.
When it was first introduced in 1995, it was considered as more of a toy than an essential development tool.
Before hopping onto one of the frameworks you might want to answer the next question for yourself first.
Wait a sec.
Let me explain.
This leads to a reduction of development, debugging and testing time.
In theory you do not need any Framework to develop.
So when it comes to creating your own projects you can choose how you want to handle things.
Looking over to the professional world of coding you will notice that nearly all Web Development job listings require some kind of Framework.
Well, as you know time = money.
So, more time = more money.
This means fast time to lambo.
As mentioned, Frameworks speed up the whole chain of development and thereby save you a lot of time.
This means you can use a framework without having to learn complicated new processes or languages.
What is the difference between Libraries and Frameworks?
Here’s a quick and easy to understand explanation
A library performs specific, well-defined operations.
A framework is a skeleton where the application defines the “meat” of the operation by filling out the skeleton. The skeleton still has code to link up the parts but the most important work is done by the application.
That’s enough for now and to understand the next aspect.
Popular Front-End Frameworks are
Its goal is to augment browser-based applications with model–view–controller (MVC) capability, in an effort to make both development and testing easier.
Angular can be used in combination with other frameworks like React, Vue, Ember, or even jQuery.
It is maintained by Facebook and a community of individual developers and companies.
React can be used as a base in the development of single-page or mobile applications.
Complex React applications usually require the use of additional libraries for state management, routing, and interaction with an API.
Vue.js is one of the latest players in the front-end frameworks scene.
Vue.js is a framework for building user interfaces. It’s very simple, flexible, and easy-to-use, similar to jQuery and Bootstrap.
According to Wikipedia about 83 whereby some are not maintained any more.
I also wanted to clear up some vocabulary terms that get confused between frameworks and libraries.
Before I jump off I would like to know one thing.
Just tweet me