You didn't follow the link, did you? It's a situation that's called "a tragedy of the commons", which doesn't mean it's a tragedy.
And anyhow, it's not about battery life, but applications using more than their fair share of memory, IO or other resources contribute to starvation for other apps that run at the same time, possibly causing crashes in other apps when they cannot allocate memory (because they're well behaved and allocate when needed and free when done), cannot update alarms in time, can't take a phone call(!), can't AV scan an incoming e-mail, or a million other things that can go wrong if too many apps on a system are hogs.
added to the fact that not all code needs to be optimized, only the little portions that perform the most critical tasks.
That this is false is my point - it's only true if your app is the only app on a system. On a shared embedded system, the portions that don't do critical tasks are just as important to optimize for the rest of the system.
Because there's no penalty to your own app, it becomes a tragedy of the commons.
To follow up on my own post, what we see in environments like the Android world is a tragedy of the commons. If everybody played nice, everybody would benefit. But there's no penalty to yourself for being greedy, so you are. And so are all others.
Android really needs something like strictly enforced cgroups.
Even though it's unrelated with my original post, you are saying that not going native is worse because it uses more CPU cycles/battery?
Explain to me why, for decades, the industry used J2ME, Java (Android) and now ObjC (Apple). I guess the entire mobile industry is selfish and greedy?
Of course they are. But that's beside the point. Development is a trade-off - you have to work with the market you have, within deadlines that means you'll sell, and developers you can find and afford. So yes, you make do with what makes the task feasible.
But you don't have to make it any worse than necessary by allowing bloat and doing things inefficiently. Adapting a mindset that you do work in a shared embedded environment, and do things frugally doesn't incur a great cost.
You probably didn't understand GP, though, the message is that you don't need to optimize something that doesn't consume enough cycles be a performance problem.
It's not just about cycles. It's also about resource use in a shared environment. The key word being shared. Whether something doesn't impact your own application isn't the problem - unless you have thought about how it could impact other applications and the overall system, you haven't done your job.
It's impossible to personally attack an Anonymous Coward.
But I'm glad you recognize what you are doing.
As for "What wasting", I asked you(?) to re-read the guy's second paragraph, but this was apparently too hard. So let me quote it:
Any attempt to raising a point about how you don't need to optimize everything but only few critical zones of your code (what matters), or that a cache wasting algorithm can end up being faster anyway just because it's more efficient, immediately results in myself being dismissed or treated as ignorant because, something inefficient is obviously inefficient and I must be stupid for not realizing that.
That wasting. Right there.
Re-read his second paragraph, AC.
Or did you just intend to troll and see how many moderators you could trick?
In a letter posted on its website [ http://www.aclu.org/blog/human-rights-national-security/us-actions-snowden-case-threaten-right-seek-asylum ], the ACLU said that the prospect of sanctions raised by the US government are in danger of ruining a system that offers solace to the outspoken.
"In the case of Mr Snowden, the United States has interfered with his right to seek asylum in two significant ways. First, the US revoked Mr. Snowden's passport. While this action does not render Mr. Snowden 'stateless' (because he is still a U.S. citizen), it does make it extremely difficult for him to travel or seek asylum, especially in countries that require asylees to be present in their territory at the time of the request," they wrote.
"Second, while the United States is within its rights to seek Mr Snowden's extradition to face charges in the United States, diplomatic and law enforcement efforts to extradite him must be consistent with international law. It appears that US efforts have prevented Mr Snowden from receiving fair and impartial consideration of his application for asylum in many of the countries to which he reportedly applied."
"US actions (including whatever role the United States played in the incident involving President Morales' plane) have arguably strengthened Mr Snowden's claims for asylum based on political persecution," they added.
"In addition to infringing on Mr Snowden's right to asylum, US actions also create the risk of providing cover for other countries to crack down on whistleblowers and deny asylum to individuals who have exposed illegal activity or human rights violations. That's a very dangerous precedent to set."
The sort of person who continues to believe these things work is the sort of person who believes that magnet motors can deliver "free" power.
So we are back at the OP, thinking how bad-ass we are. Then we get the idea to play with the kit some more. We tested our hands, HESCO barriers, lunch meat, hmmwv windows... everything tested positive
Ah. We had the same problem with exploding cans of lunch meat. No, really, after being transported on a Hercules and stored in heat for a couple of days, we would often enough hear a "pop" or "pffft". And if we didn't clean the "savory juices", the stench would start.
The guys who smuggled in pizza made a fortune.
How do you use a portable GPS as a screen saver for your car? Or an X-Acto knife as a screen saver, for that matter?
I use Rain-X on top of the screen protector. It works wonders for resisting fingerprints, and lasts for a long time as long as you only use clean water when wiping it - never alcohol.
Carnuba hard wax is even better, but you have to mask the edges and speaker hole with tape until it's buffed, or you'll get white residue. Apply 2-3 times, and you'll have the slickest and clearest display possible.
It's because they take their phone with them when they go out getting very drunk.
My mom got a 700 dollar phone, and within one week had shattered the 'screen'.
And from this, ladies and gentlemen, we can conclude...
The problem is that your baby is not the only thing running on the system. When you waste resources, you do it on behalf of everything else that runs too. Even if your baby isn't doing anything critical when you waste it.
It only takes one selfish programmer to screw up an embedded system. You are he.
Torque is cheap.