|Submited on :||Wed, 10th of Oct 2018 - 17:18:34 PM|
|Post ID :||9mxvw8|
|Post Name :||t3_9mxvw8|
|Post Type :||link|
|Subreddit Type :||public|
|Subreddit ID :||t5_2t7no|
How code runs can dramatically differ between two apps, even if the developers are implementing the same task. DiffProf catches these differences in the "call trees" of similar tasks, to show why the messaging feature of one messaging app consumes more energy than another messaging app. DiffProf then reveals how to rewrite the app to drain less battery.
And looking at a map of Africa and Europe, you can clearly see that Africa is poorer because of more dessert! Why did nobody think of this before?
Efficient interactive applications are largely event driven. They spend most of their time sitting around and waiting - with almost no battery usage.
Why don't developers write good event-driven code? Because it's hard - while sloppy, looping, spinning, polling code is easy - and eats batteries alive.
Could someone help me and give me commands for my crew. I have AI for my rooms down but my crew when I try and get them to go repair reactors they don’t go back to their original room which is a weapon room. If someone could just tell me commands I should put for all of my crew that would be great.