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

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

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

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

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

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

框架为特定的问题领域提供功能/解决方案。 定义来自wiki:

计算机中的一个软件框架 编程，是一种抽象 哪个公共代码提供泛型 功能可以选择性地 由用户代码覆盖或专门化 提供特定的功能。 框架是一种特殊情况 它们是软件库 代码包装的可重用抽象 在定义良好的应用程序中 编程接口(API)，然而他们 包含一些关键区别 区分它们的特征 普通的图书馆。

维基百科(软件框架)的摘要(第一个谷歌点击顺便说一下)解释得很好:

A software framework, in computer programming, is an abstraction in which common code providing generic functionality can be selectively overridden or specialized by user code providing specific functionality. Frameworks are a special case of software libraries in that they are reusable abstractions of code wrapped in a well-defined Application programming interface (API), yet they contain some key distinguishing features that separate them from normal libraries. Software frameworks have these distinguishing features that separate them from libraries or normal user applications: inversion of control - In a framework, unlike in libraries or normal user applications, the overall program's flow of control is not dictated by the caller, but by the framework.[1] default behavior - A framework has a default behavior. This default behavior must actually be some useful behavior and not a series of no-ops. extensibility - A framework can be extended by the user usually by selective overriding or specialized by user code providing specific functionality. non-modifiable framework code - The framework code, in general, is not allowed to be modified. Users can extend the framework, but not modify its code.

您可能“需要”它，因为它在开发应用程序时为您提供了一个很好的快捷方式，因为它包含了许多已经编写和测试过的功能。原因与我们使用软件库的原因非常相似。

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

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

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

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

为了简化事情，您可以将框架视为一个除了实际功能之外完整的应用程序。你插入功能和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应用程序，服务器端应用程序等也有类似类型的框架。在每种情况下，框架提供了大量乏味、重复的代码(希望如此)，而您提供了实际的问题域功能。(这是理想状态。当然，在现实中，框架的成功有很大的变数。)

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

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.