1·Over time, this kind of "I'll code around the problem" approach encourages code bloat and lots of incompatible special-purpose APIs, which isn't a good thing.
随着时间的推移，这种“围绕问题进行编码”的方法怂恿了代码的膨胀和许多不兼容的特殊目的 API，这并不是好事情。
2·Without scripts to build images, image bloat occurs and that eats up more space and slows the system down.
如果没有构建映像的脚本，就会发生映像膨胀，导致占用的空间增加和系统速度下降。
3·Diagnose data modeling problems in the application that contribute to memory bloat.
诊断造成内存膨胀的应用程序中的数据建模问题。
4·This can sometimes lead to test case bloat, where you are running and maintaining tests simply because they were easy to create.
因为测试用例易于创建，您能够简单地运行和维护测试，这有时会导致测试用例膨胀。
5·CSS bloat is when you have rules in your sheet that are never used-bad, but not awful-or rules that contradict or override each other-really annoying, and potentially a big problem.
当您具有从未使用过的样式表规则(糟糕但不可怕)或互相冲突或覆盖的规则时，确实会让人心烦，而且是一个潜在的大问题，CSS膨胀就会发生。