The program energy efficiency optimist's view
Despite what I wrote last entry , I think thatthere is an energy efficiency optimist's view and that it has a lot ofvalidity. It goes like this:
First, there are an increasing number of interesting devices on whichpower efficiency really does matter significantly, either because itsaves you money (such as compute clouds where you are charged veryprecisely for resource usage) or because it lets you run at all (laptopson battery power, low-power netbooks, cellphones, and so on).
Second
愛金錢愛義氣—兩全其美版(plus微弱笑一笑)

The cost of program energy efficiency
There's been somewhat of a movement of late to make programs be energyefficient (both for applications that might be running on laptops andfor applications that might run in a cloud computing environment withdetailed charging). This all sounds very good and worthwhile, and hardto argue against.
But it has a problem (the same problem as always, really). Ingeneral, such efficiency is not free since development time is notlimitless. Saying that applications should be optimized to be 'green' inthis way
一周大事
我們擁有同樣的黎明與黑夜
在經濟開了個新欄目,在評論版寫流行書,雜事纏身都不知自己做不做得來,但和編輯 leona 傾完,被電得頭暈暈,只覺「有新野不妨一試!」回來乖乖交文。然後我已暗暗下定決心,一定要讚美leona,以示我讚美女子的能力不會
Encapsulation may be in the eye of the beholder
Here is an interesting question: is getloadavg() a more orless encapsulated way of getting the load average than (onLinux) reading /proc/loadavg ? I wound up thinking aboutthis in the aftermath of feeling rueful about discovering Python's interface to getloadavg() ,and I don't think it's as simple as I made it out to be in my originalentry .
For me, what it comes down to is different perspectives. An interfacelike getloadavg() is nicely encapsulated for
stay tune
