And it has 4 900MHz ARMv7 cores. Unless you're running something compute-intensive that saturates all four of those cores, the excess CPU capacity combined with the relatively slow SD storage means you probably won't even notice the overhead.
You'd hope you could at least melt that case down once the Apple Watch 3 comes out, but the ceramic material that's mixed in might even make that hard.
Even if it was a hijack, I think all signs currently point to a hijack resulting in a crash (vaguely similar to what happened in the case of Ethiopian Airlines Flight 961). It seems like it'd be pretty hard to find an 11,000 foot runway to land on where your giant 777 wouldn't be noticed.
A fire is highly unlikely; Inmarsat continued to pick up ACARS pings/handshakes once every 70-90 minutes until roughly 8am, some seven hours after radar/transponder contact was lost with the plane. The ACARS functionality was turned off, but the SATCOM low-level communications layer was still alive. The transponder and ACARS were also disabled at roughly the same time and no radio calls were made, which seems unlikely for a progressive fire.
There are really only three possibilities left, and all of them involve human interference: either a hijack (where the transponder/radio/ACARS was intentionally disabled), a hypoxia event (where even highly-qualified pilots can make insane decisions due to lack of oxygen, and the plane continues flying in a straight line on autopilot), a pilot suicide, or some combination of these three.
Air Crash Investigation (Mayday) did a great hour-long documentary on this whole thing; totally worth watching.
I'd expect the sandboxing improvements to land in Chromium at some point.
Anyway, Chrome being non-free doesn't mean that Debian can't include the tsync backport and let people apt-get it like any other kernel update. Apparently it's a pretty straightforward port and is useful for other things (like LXC).
If someone's making credible threats of mass violence anonymously, how about GETTING A SUBPOENA TO FIND OUT WHO'S DOING IT? It'll take a few hours at most, and you won't have to obliterate the rule of law or work to actively compromise the computer systems of privately-held US companies.
Everything you mention here probably only enters the mind of 1% of the population... All that is necessary for the triumph of evil is that good men do nothing
Pervasive government surveillance doesn't fundamentally change the way we live? Tell that to the people who now self-censor to avoid ending up on a no-travel list, the journalists whose families are repeatedly detained at border crossings on manufactured "terrorism" suspicion, the technology companies and countries who are increasingly avoiding doing business with anyone in United States, the software developers who repeatedly get their laptops and phones confiscated at US ports of entry, the international tourists who now refuse to even fly through the US on their way to somewhere else, and the giant hole in basic infrastructure funding that's instead going toward a full-take federal wiretap facility in Utah.
The social contract has already changed, and certainly not for the better.
I've seen "specs" that consisted solely of a bunch of pictures and high-level diagrams, where I would have had to be a mind-reader to figure out what was going on at the detail level. In these cases, text would have gone a long way toward explaining some of the more subtle details of an interaction/procedure/design.
I've also seen "specs" that were a giant wall of text, where I had to get out a whiteboard and draw on my own because a human being couldn't possibly keep the whole verbosely-written thing in their head at once.
You need both. Anything else is bad communication.
I've never understood how Uber drivers (or taxi drivers, for that matter) can even remotely be considered "independent contractors". The IRS says:
You are not an independent contractor if you perform services that can be controlled by an employer (what will be done and how it will be done). This applies even if you are given freedom of action. What matters is that the employer has the legal right to control the details of how the services are performed.
Uber tells drivers which passengers they may pick up. They restrict what model of car drivers can use. Drivers have freedom of action to choose which passenger to pick up, but are not allowed to pick up non-Uber passengers. Uber controls virtually all of the details of how the service is performed, how feedback is provided; drivers are obligated to comply with Uber's regulations or risk termination.
Uber's drivers are employees, by the letter and the spirit of the law. Why the IRS can't enforce this shit is beyond me.
Slashdot Mirror
And it has 4 900MHz ARMv7 cores. Unless you're running something compute-intensive that saturates all four of those cores, the excess CPU capacity combined with the relatively slow SD storage means you probably won't even notice the overhead.
And immediately send you home after triage; the $1500 bill will arrive in the mail in 4-6 months.
You'd hope you could at least melt that case down once the Apple Watch 3 comes out, but the ceramic material that's mixed in might even make that hard.
Even if it was a hijack, I think all signs currently point to a hijack resulting in a crash (vaguely similar to what happened in the case of Ethiopian Airlines Flight 961). It seems like it'd be pretty hard to find an 11,000 foot runway to land on where your giant 777 wouldn't be noticed.
A fire is highly unlikely; Inmarsat continued to pick up ACARS pings/handshakes once every 70-90 minutes until roughly 8am, some seven hours after radar/transponder contact was lost with the plane. The ACARS functionality was turned off, but the SATCOM low-level communications layer was still alive. The transponder and ACARS were also disabled at roughly the same time and no radio calls were made, which seems unlikely for a progressive fire.
There are really only three possibilities left, and all of them involve human interference: either a hijack (where the transponder/radio/ACARS was intentionally disabled), a hypoxia event (where even highly-qualified pilots can make insane decisions due to lack of oxygen, and the plane continues flying in a straight line on autopilot), a pilot suicide, or some combination of these three.
Air Crash Investigation (Mayday) did a great hour-long documentary on this whole thing; totally worth watching.
I'd expect the sandboxing improvements to land in Chromium at some point. Anyway, Chrome being non-free doesn't mean that Debian can't include the tsync backport and let people apt-get it like any other kernel update. Apparently it's a pretty straightforward port and is useful for other things (like LXC).
If someone's making credible threats of mass violence anonymously, how about GETTING A SUBPOENA TO FIND OUT WHO'S DOING IT? It'll take a few hours at most, and you won't have to obliterate the rule of law or work to actively compromise the computer systems of privately-held US companies.
Ubuntu already appears to have a seccomp-tsync backport to 3.16.x: https://lists.ubuntu.com/archi....
Nostalgia, not performance.
It's Eritrea, not Ethiopia: http://www.cbc.ca/news/politic.... Not that this makes it any better or anything, but... facts and stuff.
I miss Bram's original Python version. Lawn, off, et cetera.
Couldn't have said it any better myself.
Pervasive government surveillance doesn't fundamentally change the way we live? Tell that to the people who now self-censor to avoid ending up on a no-travel list, the journalists whose families are repeatedly detained at border crossings on manufactured "terrorism" suspicion, the technology companies and countries who are increasingly avoiding doing business with anyone in United States, the software developers who repeatedly get their laptops and phones confiscated at US ports of entry, the international tourists who now refuse to even fly through the US on their way to somewhere else, and the giant hole in basic infrastructure funding that's instead going toward a full-take federal wiretap facility in Utah.
The social contract has already changed, and certainly not for the better.
Pictures and text. Both are required.
I've seen "specs" that consisted solely of a bunch of pictures and high-level diagrams, where I would have had to be a mind-reader to figure out what was going on at the detail level. In these cases, text would have gone a long way toward explaining some of the more subtle details of an interaction/procedure/design.
I've also seen "specs" that were a giant wall of text, where I had to get out a whiteboard and draw on my own because a human being couldn't possibly keep the whole verbosely-written thing in their head at once.
You need both. Anything else is bad communication.
Uber tells drivers which passengers they may pick up. They restrict what model of car drivers can use. Drivers have freedom of action to choose which passenger to pick up, but are not allowed to pick up non-Uber passengers. Uber controls virtually all of the details of how the service is performed, how feedback is provided; drivers are obligated to comply with Uber's regulations or risk termination. Uber's drivers are employees, by the letter and the spirit of the law. Why the IRS can't enforce this shit is beyond me.