Most often I see it happening when people are using custom ROMs on Android and the kernel-dev screwed up with timings or undervolts the device a bit too much when it goes idle and it basically crashes when it goes to sleep.
I had two Desire Z that had the same problem on any rom -- custom or stock. Random power down in a few weeks without any warning. Many complaints on xda-developers and no solution.
Listening to a musician is fun. Learning to play is not.
Learning to play is fun. A lot of fun. Well, at least it was fun for me. But the moment it becomes something you MUST do instead of hobby it's not fun anymore.
. I say this because of a very real problem with solar power, night
2/3 of the energy is consumed during the day and only 1/3 at night. So the night is not the main problem of solar power generation.
In Star Trek economics however, there's two problems that are solved without even needing an economy: There are no scarce resources, and there's no need for somebody to be a producer. Why? Because you've got replicators to handle your everyday goods, holodecks to entertain you, and if you want a vacation to florida, either you can holodeck there or beam over there. And since everything is made out of deuterium, there's basically an infinite supply of everything.
Well, replicator can't produce another shoreline. So, you can't build more than X houses along the beach. Here is the scarcity. Replicator can't produce personal music teacher's lessons. Etc, etc. Things from replicator will have no value and things that can't be replicated are going to be admired and desired.
I suspect rating systems fall under similar limitations as Arrow's Impossibility Theorem [wikipedia.org], and there's no way to develop a perfect rating system. So you need to dispense with the notion that there is one "best" rating system. One is not better than another, they simply tell you different things about what the population is thinking.
It's possible to build perfect rating system based on ratings if final rating is based on personal preferences. I.e. if you upvote this page and downvote that page then all similar pages get similar up/down calculations and all search results are altered accordingly -- only for you. But it's very resource-intensive compared with today systems.
Buy a Samsung Galaxy from the Samsung store in the mall, likewise, almost no chance of a problem...
Buy Samsung and get uninstallable "Flipboard" application. You can't even disable it on non-rooted phones!
Laws will happen. Just as soon as the first death is caused by a hack (or a hack gone wrong). However indirectly. That's what it takes for average people, and thus their representatives, to pay attention and figure out that something actually does matter. Then it will be a CRISIS! and we must do something NOW!
And that's the worst part of the problem. Because they won't fix security problem, they will make it illegal to install custom rom to any wireless device.
Hitler was democratically elected
He wasn't. He was appointed by Paul von Hindenburg
That the bean counters should never be in charge of making operational decisions?
Can you guarantee in writing that no bean counters will run EVERY fucking nuclear power station? Ever?!
Oh, and don't tell me 'battery banks!' because unless someone comes up with a way of directly storing electric power that scales up very, very cheaply, it's not really a practical solution to have bank after bank after bank of Li+ (or whatever) batteries, which in way less than 20 years will have to be junked and replaced, too.
Meet the Aquion -- batteries made of manganese oxide, carbon and salt. Everything is cheap and easily mined.
Just wait another ~15 years until key patents expire.
What constitutes sufficiently strong security practices?
This is the main question. What if government mandates certain antivirus program on every computer and who cares if you run linux?
I remember the first time this happened (probably about 10 years ago), I was working for a firm and they were embracing wikis and other such tools. My manager asked me to write down our trouble shooting steps in a wiki. See this line in the logs or these symptoms, and follow these steps. I kind of surprised myself how I reduced one of my great assets to something a person could follow steps on a wiki. Obviously if a new symptom showed up, not all the steps would be there. What I mean is that before there would be a problem and it would me to the rescue. Most people didn't even know where to start. Kudos to me! I realized, I just outlined the steps that most people could now follow.
Yeah, it's easy to automate part of my job. Look, it's very easy to type 'yum update' every few days, let's write it down on that fine wiki. Most people could do my work now, eh?
But once in a while shit hits the fan and suddenly openvz contaners aren't working anymore after simple update and is there anything on that wiki about handling the problem that never happened before?..
Never say you know a man until you have divided an inheritance with him.