Top 5 things a Framework is NOT responsible for!
Tags: webdev, beginners, laravel
Published: 2023-08-02 12:49:22

We often complain that an XYZ framework is slow, made my application crappy, or even claim that the Framework won't be able to handle the high traffic! So, is a framework guilty for the allegations we put on it?

<img width="100%" style="width:100%" src="https://media.giphy.com/media/Ko8G3ryOt7A1LdEv6l/giphy.gif">

We always use Programming Frameworks to make development an easy job. But we must understand that frameworks are here to make our job easy, that's it. So, let us understand what framework is **NOT** responsible for.

### 1. Security

<img width="100%" style="width:100%" src="https://media.giphy.com/media/11fot0YzpQMA0g/giphy-downsized-large.gif">

Yes, Frameworks do provide security at various points like making your files inaccessible directly and sanitising inputs. But, ultimately it's our responsibility to make sure everything remains secure. Making folder permissions to 777 or Disabling security features of Framework just because <u>_iT's aNnOyInG!_</u>  🙄 will lead your application to destruction no matter what cutting-edge framework you use! 🤷‍♂️

### 2. Application Speed

<img width="100%" style="width:100%" src="https://media.giphy.com/media/bMdZu3fG2ZEBO/giphy.gif">

Application speed depends on the System on which the application is loaded, the traffic on the system and how optimised your code/database is to handle the traffic/host. Even the benchmark tests give you a response speed in milliseconds. If your application is taking 2 minutes to load the page, it's you! Not the framework.

### 3. Optimisation

<img width="100%" style="width:100%" src="https://media.giphy.com/media/19dm2McJ6qsxCNgZwT/giphy.gif">

There's a Kaplan's law:

> Give a boy a hammer and everything he meets has to be pounded

Frameworks provide you with a lot of tools. That doesn't mean that you have to use them all to get your things done! If the new shiny feature you are using is taking a lot of resources, just skip it. Not every feature is worth using. It depends on your problem statement. True optimisation lies only in using the right method at the right moment.

### 4. Extensibility

<img width="100%" style="width:100%" src="https://media.giphy.com/media/26BkNRBRwdXfGsAlW/giphy.gif">

Writing extensible apps are totally in the hands of the developer. Frameworks always provide extensibility out of the box. That is why we can build our code on them. But we have to make sure that whatever we are building, must be extensible. **Pro-Tip:** To excel in creating extensible applications, get your basics of OOPs cleared and practice SOLID principles.

### 5. Errors and exceptions

<img width="100%" style="width:100%" src="https://media.giphy.com/media/3oz8xYzLEsMEOWwYzS/giphy.gif">

Frameworks can provide you with great debugging and testing tools. But, It is we, the developers who have to make sure that our code has no errors and all the possible exceptions are properly managed.

So, if you're ditching a framework because of any of the above-mentioned issues, think again...

<img width="100%" style="width:100%" src="https://media.giphy.com/media/777Aby0ZetYE8/giphy.gif">

Happy Coding!