A web framework is a collection of scripts, hosted on a web platform such as Internet Information Services (IIS) (on Windows) or Apache (on Linux), and calling the same script using front-end web-based languages such as HTML.

There are times when people ask why we want to migrate our current scripts or create scripts on a web framework. The answer is very simple. A web framework ensures that our scripts are used by multiple end users using just the browser. This gives the programmer the independence to code the script on their preferred platform (such as Windows or Linux), and people can use the scripts on their choice of browser. They don't need to understand how you have written the code, or what you are calling or using in the back-end, and of course, this ensures that you prevent your code from being directly visible to end users. 

Let's say  you have written a script that calls four or five libraries for specific tasks. There are general libraries, but as we have seen in previous chapters, some specific libraries need to be installed for the tasks. In this case, if you want to ensure that end users can execute your script, they need to install the same libraries on their machines. Also, they need to be running a Python environment on their machines, without which the scripts would not run. So, to run a small script of let's say five lines, users need to customize their environment by installing Python, installing libraries, and so on. 

This might not be feasible for a lot of users because of restrictions on their machines (such as installation not being allowed), so even though there is a requirement to run the scripts for those users, they would be unable to use the scripts, which would effectively lower efficiency. But the same users, if given the option, could easily open the browser of their choice and use those scripts like opening any other web page, which would ensure that our scripts bring greater efficiency to the tasks.