DEV Community

Cover image for Frameworks:The good, the bad and the ugly
Gerdeth Wickham-Daniels
Gerdeth Wickham-Daniels

Posted on

Frameworks:The good, the bad and the ugly

What is a Framework?
A framework can be described as a structure for developing software applications. Frameworks act as foundations for software developers to build programs for a specific platform. They may include predefined classes and functions, libraries of bundled code, software modeling and APIs.

Common Frameworks
Some common frameworks are listed below:

  • Angular
  • React
  • Bootstrap
  • Flask
  • Ruby on Rails

The Good
Software developers use frameworks because they streamline the development process which leads to an increase in efficiency. They make code more readable and reusable. Developers can therefore spend more time on problem-solving and collaboration without compromising the turnaround time of web-applications.
Frameworks also provide an added layer of security. They do so with built in security features against common attacks and data tampering.

The Bad
There is also a downside to using frameworks. Frameworks have predefined classes, functions, libraries and code which are not necessary for all projects. While these unnecessary files can be deleted, it can be time consuming and overwhelming to do so. In some cases it's more efficient not to use a framework.

The Ugly
The truth is frameworks are lovely tools. In my opinion, a developer should be proficient in a programming language before attempting to learn a framework. Know the basics before moving on to the fancy stuff!
Frameworks can be combined in a web-application:one framework on the frontend and another on the backend. However, just like everything in web-development, it requires practice. I would recommend that beginners use different repositories for the frontend and the backend because it can be a nightmare keeping up with two different frameworks in one repository.

Discussion (0)