I'm very late to answer it. But, I would like to share one example, which I only thought of today. If I told you to cut a piece of paper with dimensions 5m by 5m, then surely you would do that. But suppose I ask you to cut 1000 pieces of paper of the same dimensions. In this case, you won't do the measuring 1000 times; obviously, you would make a frame of 5m by 5m, and then with the help of it you would be able to cut 1000 pieces of paper in less time. So, what you did was make a framework which would do a specific type of task. Instead of performing the same type of task again and again for the same type of applications, you create a framework having all those facilities together in one nice packet, hence providing the abstraction for your application and more importantly many applications.

我不确定“框架”是否有一个明确的定义。有时，一组很大的库被称为框架，但我认为这个词的典型用法更接近于aioobe带来的定义。

这篇非常好的文章总结了一组库和一个框架之间的区别:

框架可以定义为一组库，它们说“不要给我们打电话，我们会给你打电话”。

框架如何帮助您?因为您不需要从头开始编写一些东西，基本上只需扩展一个给定的工作应用程序。通过这种方式，您可以获得很高的生产率——有时最终得到的应用程序可能比您在相同时间内自己所做的要复杂得多——但您通常会牺牲很多灵活性。

在最低的层次上，框架是一个环境，在其中您可以使用一组工具

这些工具以库、配置文件等形式出现。

这个所谓的“环境”为您提供了基本的设置(错误报告、日志文件、语言设置等)……它可以被修改，扩展和构建。

人们实际上不需要框架，这只是想要节省时间的问题，而其他人只是个人喜好的问题。

人们会证明有了框架，你就不必从头开始编码了。但这些只是人们混淆了库和框架。

我在这里没有偏见，实际上我现在使用的是一个框架。

一个简单的解释是:框架是一个可以围绕它构建应用程序的支架。

A framework generally provides some base functionality which you can use and extend to make more complex applications from, there are frameworks for all sorts of things. Microsofts MVC framework is a good example of this. It provides everything you need to get off the ground building website using the MVC pattern, it handles web requests, routes and the like. All you have to do is implement "Controllers" and provide "Views" which are two constructs defined by the MVC framework. The MVC framework then handles calling your controllers and rendering your views.

也许不是最好的措辞，但我希望它有帮助

已经有很多很好的答案了，但让我看看我是否能给你另一个观点。

为了简化事情，您可以将框架视为一个除了实际功能之外完整的应用程序。你插入功能和PRESTO!你有一个应用程序。

Consider, say, a GUI framework. The framework contains everything you need to make an application. Indeed you can often trivially make a minimal application with very few lines of source that does absolutely nothing -- but it does give you window management, sub-window management, menus, button bars, etc. That's the framework side of things. By adding your application functionality and "plugging it in" to the right places in the framework you turn this empty app that does nothing more than window management, etc. into a real, full-blown application.

对于web应用程序，服务器端应用程序等也有类似类型的框架。在每种情况下，框架提供了大量乏味、重复的代码(希望如此)，而您提供了实际的问题域功能。(这是理想状态。当然，在现实中，框架的成功有很大的变数。)

我再次强调，这是对框架的简化观点。我没有使用像“控制反转”之类的可怕术语，尽管大多数框架都内置了这样可怕的概念。既然你是初学者，我想我就不给你行话了，用一个简单的比喻。

一个框架帮助我们使用“已经创建的”，一个比喻可以是，

把地球上的物质想象成编程语言，

举个例子，“相机”是一个程序，你决定创建一个笔记本。你不需要每次都重新创建相机，你只需要使用earth框架(例如技术商店)将相机并将其集成到你的笔记本电脑中。