框架与 SDK [英] Frameworks vs. SDKs

问题描述

框架和 SDK 有什么区别?以 MS 平台 SDK 和 .NET 框架为例.两者都有 API，都隐藏了它们的内部工作原理，并且都提供了否则可能无法快速/轻松访问的功能(换句话说，它们服务于现实世界的目的).

What is the difference between a framework and an SDK? Take, for example, the MS platform SDK and the .NET framework. Both have API's, both hide their inner workings, and both provide functionality that may not be quickly/easily accessible otherwise (in other words, they serve a real-world purpose).

那有什么区别呢?它主要是语义营销游戏，还是在期望开发人员与软件交互的方式(以及开发人员如何期望软件的行为)方面存在实际差异?预期一个比另一个更高还是更低，等等?

So what's the difference? Is it primarily a marketing game of semantics, or are there actual differences in how developers are expected to interact with the software (and conversely, how the developers can expect the software to behave)? Is one expected to be higher- or lower-level than the other, etc?

谢谢！

这个问题一般适用于 SDK 和框架，而不仅仅是上面提到的两个.

This question applies to SDKs and frameworks in general, not just the two mentioned above.

推荐答案

SDK 有望提供针对特定系统资源或功能进行编程的工具.不一定是框架(尽管 .NET 提供了一整套工具，例如编译器等 - 但无论如何这些工具都是必须的).

An SDK is expected to offer tools to program against a certain system resource or feature. A Framework not necessarily (although .NET offers a whole set of tools such as the compilers, etc - but these are mandatory for it to work anyways).

因此，您可以开发一个仅由库组成的框架，但如果您将其称为 SDK，您将需要提供一些东西来支持开发.

So, you could develop a Framework consisting solely of libraries, but if you call it SDK you will be expected to offer something to support development.

这篇关于框架与 SDK的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！