Spring Framework源码阅读的前章 -- 设计原则

前章

“我应该怎么看Spring的源码内容?”
我相信很多人都有这样的疑问，虽然已经有很多培训机构都会有相关内容。吃惯了成品菜，却忽略了怎么做菜，这种感觉总是让人彷徨。

我先按照我的思路探索，如果各位看官姥爷有什么意见和建议，希望能留下您宝贵的意见。
本专栏内容仅代表个人看法，君莫笑。

Spring Framework 设计原则

• Provide choice at every level. Spring lets you defer design decisions as late as possible. For example, you can switch persistence providers through configuration without changing your code. The same is true for many other infrastructure concerns and integration with third-party APIs.

在每一个层次上提供选择。Spring允许您尽可能推迟设计决策。
例如，您可以通过配置切换持久性提供程序，而无需更改代码。许多其他基础设施问题以及与第三方API的集成也是如此。

• Accommodate diverse perspectives. Spring embraces flexibility and is not opinionated about how things should be done. It supports a wide range of application needs with different perspectives.

容纳不同的观点。
Spring拥抱灵活性，不固执己见 它支持广泛的应用程序需求， 不同的视角。

• Maintain strong backward compatibility. Spring’s evolution has been carefully managed to force few breaking changes between versions. Spring supports a carefully chosen range of JDK versions and third-party libraries to facilitate maintenance of applications and libraries that depend on Spring.

保持强大的向后兼容性。
Spring的进化经过精心管理，在不同版本之间几乎没有突破性的变化。Spring支持精心选择的一系列JDK版本和第三方库，以便于维护依赖于Spring的应用程序和库。

• Care about API design. The Spring team puts a lot of thought and time into making APIs that are intuitive and that hold up across many versions and many years.

关注API的设计。
Spring团队花了大量的心思和时间来制作直观的API，这些API在许多版本和许多年中都是有效的。

• Set high standards for code quality. The Spring Framework puts a strong emphasis on meaningful, current, and accurate javadoc. It is one of very few projects that can claim clean code structure with no circular dependencies between packages.

为代码质量设置高标准。
Spring框架非常强调有意义、当前和准确的javadoc。它是少数几个可以声称在包之间没有循环依赖关系的干净代码结构的项目之一。

这段很重要，很重要，很重要