Can code be bad for the planet?可以代码是坏为地球?

October 14th, 2007 | by ian | 2007年10月14日|由伊恩|

Alistair阿利斯泰尔 has an有一 interesting post on Earth2Tech有趣的职位就earth2tech , the thesis of which is that inefficient coding practices can lead to environmental harm. ,论文,其中是没有效率的编码的做法可能导致的环境损害。

I almost misled myself into thinking AC is blaming virtualization and SaaS/IaaS (infrastructure as a service) on creating such inefficiencies.我差点误导了6-6平,比赛进入交流思想,是怨天尤人,虚拟化和saas / iaas (基础设施作为一个服务) ,创造这样的效率低下。 Rather, he skipped past the obvious environmental benefits of server consolidation (improved resource utilization) and service centralization (via economies of scale) and instead builds on the consequences: code inefficiencies become more obvious when you’re no longer massively overprovisioning hardware.相反,他跳过去明显的环境效益的伺服器整合(改善资源利用)和服务集中(通过规模经济) ,而是建立在后果:代码效率低下更加明显当您不再大量overprovisioning硬件。 This is an opportunity as much as a challenge.这是一个机遇,更是一种挑战。 Bad code did matter previously, but not to the extent that is forseen: we’re scaling web applications to a much larger degree than ever before.坏的代码没有以前的事,但不能在多大程度上是forseen :我们正在结垢的Web应用程序,以一个更大的程度比以往任何时候都。 There are more users, and inefficiencies are multiplied.有更多的使用者,和效率低下是成倍增加。

So it is great news that virtualization and on demand infrastructure will allow us to focus more on code efficiency since as Alistair (incidentally a veteran in the monitoring of applications) points out, it exposes more granular economics of computing.所以这是很大的消息说,虚拟化和对基础设施的需求,将使我们能够更专注于代码效率以来,作为阿利斯泰尔(顺便一老,在监测的应用)所指出的那样,它暴露了更精细的经济学计算。 These technologies are paving the way to greater infrastructure efficiencies and by forcing better utilization of hardware, putting more focus on the efficiency of the code that cohabits the infrastructure.这些技术铺平了道路,以更大的效率和基础设施,迫使更好地利用硬件,把更多的重点放在效率的代码cohabits的基础设施。

Increasing code efficiency has been generally unimportant except in edge cases.提高代码效率已普遍不重要,除在边缘案件。 Stability and function has been more of a concern while Moore’s law and incomplete costing of infrastructure have been more than compensating for performance.稳定和功能已更值得关注的同时,穆尔定律和不完整的成本核算基础设施已超过补偿的表现。 Rapid application development platforms proliferate based upon the abilities of modern hardware to crunch “affordably” through the multiple layers of abstraction.快速应用开发平台,基于扩散的能力,现代的硬件,以紧缩的“经济实惠” ,通过多层次的抽象。

What me worry? 我担心什么呢?

There’s definite potential for code to have an environmental impact.有一定潜力的代码有一个环境的影响。 We have an existing ecological disaster on our hands with the castoff personal computing hardware of both enterprises and consumers.我们有一个现有的生态灾难对我们的手与废弃物个人电脑的硬件,双方企业和消费者的利益。 Almost all of that computing power was wasted idling, never used, just for the ability to load Microsoft Office applications quickly.几乎所有的计算能力被闲置,浪费,从未使用过,只为有能力负荷Microsoft Office应用程序迅速。 How do we acheive more efficient code?我们如何实现更有效的代码? As more people rely more on computing, the costing of which is becoming more accurate and granular, and as the barriers of entry for developers drop, we should witness an evolutionary process at work battling inefficiency assuming:随着越来越多的人更多地依靠计算,成本是越来越准确和颗粒,并作为屏障进入开发商下降,我们应该看到一个渐进的过程在工作中战斗效率低下假设:

  • large population of users人口众多的用户
  • competing applications竞争的应用
  • rapid generation spans with modification快速一代跨度与改造
  • market exerts selective pressure市场施加的选择压力

While I think these evolutionary forces are already at work, the selective pressures have been weak, the environment has been overly abundant leading to a Cambrian explosion of inefficiencies that eventually will be represented in costs that the market will react to, assuming that the market has the freedom to do so.而我认为这些进化的力量已经在工作中,选择性的压力,已薄弱,环境已过于丰富,导致了寒武纪爆炸,效率低下,最终将出席在成本,市场会作出反应,假设市场自由这样做。 This is where intellectual property issues and the “one platform to rule them all” attitude may present a bit of a speedbump, but only that.这是知识产权问题和“一个平台,以统治他们的所有”的态度,可能会有点一speedbump ,但只有这一点。

Alistair’s most important point is highlighting that proper costing of computing is essential: if we want to minimize environmental impact we need to measure the efficiency of work performed by applications and the true cost of the resources they consume.阿利斯泰尔的最重要的一点是强调指出,适当的成本计算是必不可少的:如果我们要尽量减少对环境的影响,我们需要衡量工作效率执行的申请和真正成本的资源消耗。 My conjecture is that an evolutionary process of anthropogenic artificial selection, automated or not, should optmize resource utilization.我的猜想是一个渐进的过程的人为人工选择,自动或没有,应optmize资源利用率。 This rests upon the premise of a competitive market, which I believe we are just starting to see in the world of software.这取决于的前提下一个竞争性的市场,我相信我们刚开始看到在世界上的软件。

For now I’m much more concerned with how poorly conceived code can compromise privacy, and restrictive code that restricts our freedom of communication and innovation.现在我更关心如何不善的构思代码可以妥协的隐私,和限制性的代码,限制了我们的通讯自由和创新的过程。 But those are stories for another post.但这些故事的另一个职位。

Post a Comment张贴评论