Why, exactly, do developers decide the native OS methods for finding and starting apps are insufficient and must be replaced with some ill-conceived launcher app? Google is far from the only offender here.
Liam specifically rescues cobalt and lithium from the battery, gold and copper from the camera, silver and platinum from the logic board and the aluminum enclosure, as well.
It's an arm that disassembles iPhones. Sure, separating parts is a first step to recovering raw materials, but they make it sound like the thing has some magic nano-disassembler ray.
The thing is, Apple will sell something like 8 iPhones per second. Think of how many workers it takes to *assemble* iPhones; it would take a similar army of these to dismantle each one part by part.
But that's the key, isn't it? It's no large step from disassembling phones to assembling them; Apple likely built this as a testbed for robot manufacturing, and in the mean time, a tool for salvaging usable parts for their refurbishers. Oh, and the occasional 'aren't we environmentally conscious' video.
On the other hand, the 3Com XJACK was nice, if still rather fragile. A breakaway version that could be yanked out of the device and easily replaced would be a good solution for ultrabooks and tablets.
But wireless is where it's at in the mobile space these days, and the few mobile device makers that even bother with Ethernet probably won't for much longer. Despair not; a USB Type-C adapter will give you a nice small plug, or you can buy a wireless bridge (battery-powered, even) if you don't want to sully your devices with cords at all.
I picked up a HP gaming PC with 980Ti and 4790K last year for $950... That's the price of a low-end Surface Pro or high-end iPad.
These days the "high end" gamers are running SLI/Crossfire, and the "cost no object" ones have Triple- and Quad-GPU rigs with PCI-e SSDs, 1.5KW PSUs, water cooling, etc.
Agreed... while I think the court is correct (Android is a de facto monopoly in many countries and Google isn't shy about leveraging it to push their other services), this decision falls in the "even a stopped clock" category.
Of course, I'm sure the bribe..err..fine will be low enough that Google won't actually have to change anything.
The event can also be streamed from second-, third- and fourth-generation Apple TV set-top boxes. On a Mac, users must be running Safari 6.0.5 or later on OS X 10.8.5 or later, and PC users must use the Microsoft Edge browser in Windows 10.
In any case Pen support for the regular iPad would be nice, but unless there's some surprise addition this looks like another boring event. Apple has been busy this past year with the MacBook, Watch, iPad Pro, Apple TV, etc, but right now their entire product lineup is either too old or too new to tempt me.
Unfortunately apps that fully utilize 4 cores are few and far between, so take these numbers with a grain of salt, but the 820 seems to handle single-threaded applications better than its predecessors, putting real-world performance on par with the (admittedly 6 month old) Apple A9.
In any case, it's astounding how ARM designs have gone from a decade behind to modern PC level performance in the space of a few years—and they're not done; performance leaps year after year and for once Samsung and TSMC may beat Intel to 10nm. Intel should be worried, especially if AMD manages to become relevant again with Zen.
An Apple spokeswoman commented on the issue, referring to protective security features intended to prevent "malicious" third-party components from potentially compromising a user's iPhone as the main reason for the "error 53" message.
We protect fingerprint data using a secure enclave, which is uniquely paired to the touch ID sensor. When iPhone is serviced by an authorised Apple service provider or Apple retail store for changes that affect the touch ID sensor, the pairing is re-validated. This check ensures the device and the iOS features related to touch ID remain secure. Without this unique pairing, a malicious touch ID sensor could be substituted, thereby gaining access to the secure enclave. When iOS detects that the pairing fails, touch ID, including Apple Pay, is disabled so the device remains secure.”
She adds: “When an iPhone is serviced by an unauthorized repair provider, faulty screens or other invalid components that affect the touch ID sensor could cause the check to fail if the pairing cannot be validated. With a subsequent update or restore, additional security checks result in an ‘error 53’ being displayed If a customer encounters an unrecoverable error 53, we recommend contacting Apple support.
Online users choose content providers with web sites over content providers without web sites. Ergo, the WWW distorts competition and should be shut down.
Chrome advertises its Incognito mode as leaving no traces behind. Therefore, it should be responsible for wiping its framebuffer, just as it clears caches, cookies and history. It's like writing a file shredder that doesn't actually overwrite files, then blaming the OS and hard drive manufacturer for the oversight.
It might be nice if framebuffers and such were zeroed on release, but like overwriting files, it's a time/energy/security tradeoff. Besides, the screen isn't really protected anyway; IIRC applications on most OSes can capture the screen without even admin privileges. After apps are sandboxed into seeing only their own windows we can talk about securing the framebuffer.
Slashdot Mirror
Why, exactly, do developers decide the native OS methods for finding and starting apps are insufficient and must be replaced with some ill-conceived launcher app? Google is far from the only offender here.
It's an arm that disassembles iPhones. Sure, separating parts is a first step to recovering raw materials, but they make it sound like the thing has some magic nano-disassembler ray.
The thing is, Apple will sell something like 8 iPhones per second. Think of how many workers it takes to *assemble* iPhones; it would take a similar army of these to dismantle each one part by part.
But that's the key, isn't it? It's no large step from disassembling phones to assembling them; Apple likely built this as a testbed for robot manufacturing, and in the mean time, a tool for salvaging usable parts for their refurbishers. Oh, and the occasional 'aren't we environmentally conscious' video.
On the other hand, the 3Com XJACK was nice, if still rather fragile. A breakaway version that could be yanked out of the device and easily replaced would be a good solution for ultrabooks and tablets.
But wireless is where it's at in the mobile space these days, and the few mobile device makers that even bother with Ethernet probably won't for much longer. Despair not; a USB Type-C adapter will give you a nice small plug, or you can buy a wireless bridge (battery-powered, even) if you don't want to sully your devices with cords at all.
If history has taught me anything it's that looking silly is no hindrance to starting wars.
I picked up a HP gaming PC with 980Ti and 4790K last year for $950... That's the price of a low-end Surface Pro or high-end iPad.
These days the "high end" gamers are running SLI/Crossfire, and the "cost no object" ones have Triple- and Quad-GPU rigs with PCI-e SSDs, 1.5KW PSUs, water cooling, etc.
It would make a nice micro home server / VM box, though with those specs and dimensions it'll probably be a noisy bugger.
Also, TB 3 opens the door for an eGPU...
So they discovered FHSS. Good for them!
(Also, they may be able to mask the radar pulses, but "encrypt"? Really?)
"Oh, it must be a Google Fiber city."
Bingo.
Remind me why competition among public utilities is bad again?
In most big cities it's faster to walk 2km than drive, and Bucharest is particularly bad:
http://www.romania-insider.com...
Agreed... while I think the court is correct (Android is a de facto monopoly in many countries and Google isn't shy about leveraging it to push their other services), this decision falls in the "even a stopped clock" category.
Of course, I'm sure the bribe..err..fine will be low enough that Google won't actually have to change anything.
The event can also be streamed from second-, third- and fourth-generation Apple TV set-top boxes. On a Mac, users must be running Safari 6.0.5 or later on OS X 10.8.5 or later, and PC users must use the Microsoft Edge browser in Windows 10.
In any case Pen support for the regular iPad would be nice, but unless there's some surprise addition this looks like another boring event. Apple has been busy this past year with the MacBook, Watch, iPad Pro, Apple TV, etc, but right now their entire product lineup is either too old or too new to tempt me.
Unfortunately apps that fully utilize 4 cores are few and far between, so take these numbers with a grain of salt, but the 820 seems to handle single-threaded applications better than its predecessors, putting real-world performance on par with the (admittedly 6 month old) Apple A9.
In any case, it's astounding how ARM designs have gone from a decade behind to modern PC level performance in the space of a few years—and they're not done; performance leaps year after year and for once Samsung and TSMC may beat Intel to 10nm. Intel should be worried, especially if AMD manages to become relevant again with Zen.
Nope, sorry, that isn't true. That's not possible right now.
That's going to take a lot of mining.
Hi, are you new here?
I've always felt needed.
I thought it translated to "Springboard Expansion Slot", but I guess I'm showing my age.
Basically like everything else in the world?
Yes, that's the problem.
TIL lasers have their own band in the EM spectrum.
Apple's response, by way of MacRumors:
An Apple spokeswoman commented on the issue, referring to protective security features intended to prevent "malicious" third-party components from potentially compromising a user's iPhone as the main reason for the "error 53" message.
We protect fingerprint data using a secure enclave, which is uniquely paired to the touch ID sensor. When iPhone is serviced by an authorised Apple service provider or Apple retail store for changes that affect the touch ID sensor, the pairing is re-validated. This check ensures the device and the iOS features related to touch ID remain secure. Without this unique pairing, a malicious touch ID sensor could be substituted, thereby gaining access to the secure enclave. When iOS detects that the pairing fails, touch ID, including Apple Pay, is disabled so the device remains secure.”
She adds: “When an iPhone is serviced by an unauthorized repair provider, faulty screens or other invalid components that affect the touch ID sensor could cause the check to fail if the pairing cannot be validated. With a subsequent update or restore, additional security checks result in an ‘error 53’ being displayed If a customer encounters an unrecoverable error 53, we recommend contacting Apple support.
The last link is a nice touch.
Online users choose content providers with web sites over content providers without web sites. Ergo, the WWW distorts competition and should be shut down.
Chrome advertises its Incognito mode as leaving no traces behind. Therefore, it should be responsible for wiping its framebuffer, just as it clears caches, cookies and history. It's like writing a file shredder that doesn't actually overwrite files, then blaming the OS and hard drive manufacturer for the oversight.
It might be nice if framebuffers and such were zeroed on release, but like overwriting files, it's a time/energy/security tradeoff. Besides, the screen isn't really protected anyway; IIRC applications on most OSes can capture the screen without even admin privileges. After apps are sandboxed into seeing only their own windows we can talk about securing the framebuffer.
To be replaced by "Does the light go out when you turn off the camera?"