UC知道哪位好心人帮我翻译成中文？小弟十分感谢
来源：百度知道 编辑：UC知道 时间：2024/06/01 23:58:07
SPAGHETTI DESIGN IN NETBEANS
Similar spaghetti-related problems happened to NetBeans. Though the application was always designed to be modular, it used to have one huge module called OpenAPIs, which contained all the APIs for communication between the other modules. From today’s point of view, this was ridiculous. However, in those days, from 1997 to 2000, no project in Java was as modular as NetBeans. It took time for us to realize that there would be scalability problems in terms of maintaining such huge and monolithic APIs. In 2000 or so, it became clear that each module would need to be able to export its own API. Modules created after that date now do exactly this. However, some of the large monolithic OpenAPIs remained.
The situation gradually worsened. In each release, something needed to be fixed. Developers started adding inner dependencies between logical parts of the OpenAPIs, instead of leaving them separated. The situation was becoming comparable to java.la
Similar spaghetti-related problems happened to NetBeans. Though the application was always designed to be modular, it used to have one huge module called OpenAPIs, which contained all the APIs for communication between the other modules. From today’s point of view, this was ridiculous. However, in those days, from 1997 to 2000, no project in Java was as modular as NetBeans. It took time for us to realize that there would be scalability problems in terms of maintaining such huge and monolithic APIs. In 2000 or so, it became clear that each module would need to be able to export its own API. Modules created after that date now do exactly this. However, some of the large monolithic OpenAPIs remained.
The situation gradually worsened. In each release, something needed to be fixed. Developers started adding inner dependencies between logical parts of the OpenAPIs, instead of leaving them separated. The situation was becoming comparable to java.la
类似意大利有关的问题发生的NetBeans 。虽然应用始终是模块化设计，它采用了一个巨大的模块称为OpenAPIs ，其中载有所有的API之间的通信的其他模块。从今天的角度来看，这是荒谬的。然而，在那些日子里，从1997年到2000年， Java中没有的项目是作为模块化作为NetBeans 。它需要时间，我们认识到，将有可扩展性问题方面保持如此庞大的和整体的API 。在2000年左右的时间，人们清楚地看到，每个模块就必须能够出口其自己的API 。模块建立在该日期之后现在正是这一点。然而，一些大的单片OpenAPIs依然存在。
这种情况逐渐恶化。每一个版本，但需要固定。开发商开始增加内在逻辑部件之间的依赖关系的OpenAPIs ，而不是让他们分开。局势变得比较java.lang提到java.awt 。有时这样做是作为一个执行机构内部的详细的方法和有时甚至暴露在空气污染指数！到2003年，我们已enough.We了第一个重要步骤：我们清理掉不必要的交叉引用和分裂
汇编OpenAPIs到逻辑部分。然而，由此产生的二进制仍或多或少一个大的模块。这至少防止进一步破坏的代码之间的不必要的依赖逻辑部分。但是，又两年整个单片模块完全消失。