Having control over the Play Store is the key element to keeping security exploits from being a nightmare, since phone hardware vendors are clearly not ever going to do software updates well. But if you can block the main way seriously bad malware gets onto the system in the first place--installing rogue apps--you can limit the damage.
Samsung has an inescapable problem. If they make their additions to the phone small enough to apply easily to upstream Android, they won't have a distinct enough offering to really distinguish from stock Android. If they modify their platform with a lot of large changes, now they have a hard merge problem as new upstream Android releases come out.
If you are consuming an upstream software distribution, you have to innovate faster than they do in order to produce something really different that is still useful. So far Samsung seems to have navigated that well enough to satisfy customers, with only some complaints about slow upstream merges. But they'll always be facing this problem where serious innovation will fork Google's Android so much that they're stuck with a lot more R&D work to support the result.
The whole reason Android has become successful is that Google has so far done a good job at that task, something no phone hardware vendor was handling before (except Apple). The idea that Samsung will succeed in outperforming Google here, that's an idea that seems to ignore the battered trail of competitors like Nokia, Blackberry, and Motorola. Building a successful phone platform is a much harder problem than any phone hardware manufacturer faces; Google has managed it; and Samsung is going to need a lot of good luck to compete directly at that job.
USB is expected to match current Thunderbolt speeds later this year. Sluggishness updating the USB standard meant Apple got a short period where Thunderbolt was so much faster than anything else around that it enabled some new applications. But currently available 5Gbps USB 3.0 has already closed the important part of that gap, eliminating most of the "couldn't possibly be connected on USB" gap. High resolution outboard video is the only thing really left in that category.
The chunk of the market that needs 4K video processing will still need Thunderbolt speeds, but not other application does. I can't imagine any music software that needs more than 5Gbps, which means the idea of artists and producers walking into a studio can easily happen on USB3 instead. When Apple introduced Thunderbolt, musicians had outgrown USB2, but they're unlikely to ever outgrow USB3. Why would manufacturers of music hardware build anything on Thunderbolt when they can make a cheaper product based on USB3 and sell it into Mac and PC markets?
The main risk is that the split in resources will cause both projects to be not good enough. Being perceived as a downstream version of another project, but with additions incompatible with their terms, that doesn't necessarily favor either end. There's a similar relationship between Debian and Ubuntu that turned out to make both more popular. What LibreOffice is trying to do is more like the XFree86 vs. Xorg split though.
Unfortunately, OpenOffice can't do the reverse without switching their license.
It's not really unfortunate when it's by design. LibreOffice wants to make Apache OpenOffice become so redundant the project just gives up. This is how open source developers protest work that they feel is being done poorly. They fork the project in a way that allows only one-way code copying, and then try to starve the original of resources and its user base.
Time Machine keeps an event store journal of changes, the process is described at How Time Machine Works its Magic. What you're describing might be a "deep scan" pass. It's also possible you're touching a lot of directories with updates, which makes the optimization they apply not as useful.
There are cases where the event store makes Time Machine backups nearly instant, which is never the case for rsync based approaches being complained about here.
Specifically how DRBD handles recovery after an outage of the replication network. The situations where the disk isn't plugged in will look just like the network outage scenario DRBD handles. I'm not sure whether this will be more or less efficiency than the mdadm bitmap approach outlined above, but those are the two main ways people do this specific operation.
It's hilarious how Apple finally dropped Firewire only to adopt Thunderbolt, which might as well be called Firewire 2011. I really like Thunderbolt as a cost no object design, but what the market has proven every single time is that an I/O chipset has to be cheap and easy to license to succeed. USB 3.0 made Thunderbolt obviously obsolete before the first Apple model supporting it shipped.
Can you believe someone thinks this is about "modular, external upgrades"? Replacing on-board Ethernet with the Thunderbolt to Gigabit Ethernet Adapter is one of the most transparent margin increasing cash grabs I've ever seen.
I haven't found much value to "reveal codes" once I started consistently applying style sheets to all text. Micro-managing the codes that go into the document encourages complicated one-off edits, and doing that is where most of the document structure problem I see originated from in the first place. I look at a list of all the styles used in the document, and if there's anything that looks out of place I'll kill it from that viewpoint. That approach converges on a known clean document in way that takes a lot less individual code review work. YMMV, but I'd never go back to staring at formatting codes again now that I've embraced styles.
Why use something as complicated at LaTeX if you don't care about formatting? Use something that looks like plain text until you want to apply formatting, like reST, Markdown, or Asciidoc. Using LaTeX as your example of a non-WYSIWYG editor just scares people off, when they could just \relax and type simple text.
Possibly, but there are a lot of tasks that only see about a doubling of speed. A C++ port is only likely to speed things up, while a GPU one is certain to. (Presuming the assumption about parallel execution is correct)
Publisher Heise is a popular and well regarded brand name for tech news in German. The English "The H" was trying to leverage their existing brand reputation. It didn't work out, but I can understand why they tried using that name to try. It's not as bad as the dubious reasoning behind some of the poorly chosen open source project names. (LibreOffice, I'm looking at you too)
The last major Android update applied to Nexus phones was 4.2.2, which rolled out in Februrary. If you haven't gotten an update in six months, something is wrong with your setup. My Nexus phone has also gotten multiple revamps to various Play applications in the last few months, which was most noticeable to me in a complete redesign of the Play Music application. The last update there I know of was a month ago. I'm not certain what form (if any) the fix for this exploit has been pushed to the phones yet--could be a core update or fix in a play app--but your claim that they haven't changed anything recently isn't true.
You know what else used to be a nutball theory? That the NSA had vast spying capabilities being used to monitor large swaths of the Internet all of the time.
There's plenty of historical examples that show lists of citizens meeting some criteria turning into a list of people to inflict government action upon. We don't even have leave the US to find one. It was the US Census database that was used to round up Japanese citizens for internment to fulfill Executive Order 9066. If I have an unusual political belief--let's use the example from the TFA of advocating marijuana--I have every reason to believe that when the government collects data about my communication, it might one day use that to prosecute me for drug related offenses, and launch investigations of those I deal with too. That sort of chilling effect on political speech is why monitoring makes free political speech impossible. Any student of history knows the bad situations that leads to.
If the US government actually cared about the limits on its scope in the constitution, we would not have the Authorization for Use of Military Force Against Terrorists or the Patriot Act. When the government isn't even paying attention to its own rules on declaring war, the idea that the enumerated powers provide any limit on its scope is rather weak. A government that's let all that happen is not going to suddenly turn introspective on the vast subject of whether its recent decisions are really within its powers.
Unlike the ninth, the courts still act like the first amendment is valid sometimes, which is what makes that a better bet for waging a lawsuit.
But why chase after a complicated case involving an obscure amendment when there's a simple one available? Americans generally understand that political speech is protected by the 1st amendment. Point out that monitoring makes that impossible, and you're done, in a way that's very easy to explain to people--and therefore rally support around.
His bone density is going to be lower than someone who lives on Krypton itself. But if all of the structural components to his body, from bone to muscle to neurons, are adapted to be just plain stronger, some of that might be retained even without as much load on your body.
At this point we know just how much things like time in space degrade physical function, suggesting that a body's natural high gravity capability is trumped by recent environment stress. But the high-gravity powered Superman was the one of the 30th through 50's. The shift from a gravity powered hero to the magic yellow sun powers happened during the 60's, partly due to understanding of this area improving so much then. You can almost see how Superman's power explanations evolved in step with early space exploration.
Right, the whole yellow sun thing didn't show up until the silver age era in the early 60's. Before that he was jumping--"able to leap tall buildings in a single bound"--and they modeled the low gravity powers based on speculation about what a man on the moon would be capable of doing.
Coffee cups are a really bad example to bring up here. The warnings are there to try and dislodge ideas like the McDonald's coffee lawsuit. The reason that woman won a large judgement against McDonald's is that they were knowingly selling an unsafe product and just didn't care what happened to their customers.
So the problems leading to the warnings were not so much that people were stupid. It was that some number of corporations selling coffee were acting irresponsibly. In a social environment where legal penalties are the only way to add corporate accountability for unsafe behavior, you're kind of stuck with suing them to make a useful change. And when that happens, you can expect that those companies are going to add warnings to try and reduce their liability. That's not really connected to consumers being dumb in the coffee case.
The reason why that's a particularly bad example is that people see that sort of necessary legal action, and then apply it to shifting blame for any problem with a product. The subtle difference is that the McDonald's coffee was unfit for its stated purpose as sold, making it defective by objective measures. You cannot measure anything wrong with an Apple product because it lets you view porn. That's a subjective, moral issue rather than something you can build a factual case around.
Serious Business (TM) users are going to see the boot screen of their Linux distribution. The only people who see Tux at boot right now are ones who will appreciate the joke.
Most of the Windows laptops I look at are using 2 to 3GB of RAM. There is almost zero demand for RAM beyond 4GB among consumers, and that's absolutely correct. You have the cause/effect backwards. The migration to 64 bits wasn't slow because people couldn't get the software. It was slow because the faster hardware didn't help very much, making it impossible to cost justify putting any work into that.
Adding more RAM to machine that is only caching a few GB before a reboot will not increase its speed at all. Speed certainly wouldn't double by having twice as much RAM. The reason why people are spending money on SSD instead of RAM is because memory only helps once you've read data from disk once. There are some small uses of RAM for things like temporary files, but those are not common on consumer workloads either.
Back when all of the mass market machines were dipping into swap to run their normal application, adding RAM made them much faster. And that move was held back a little bit by the 32 bit memory limit. Those days are years in the rear view now though. I upgraded all of my laptops from 8GB to 16GB of RAM recently, and there was no responsiveness improvement for day to day work. I'm just not using more than 8GB very often, unless I get crazy with the number of web browser tabs going at once.
The Jump the Shark episode of the X-Files in 2002 was when Jumping the Shark jumped the shark. That added millions of people who started making these joke badly, and the average quality of such comments has slowly fallen of ever since. The alternate date to pick wasn't much later, which is 2003 when John Hein's book had come out. I thought it was clear we were into the boring repeat phase a little before then.
Slashdot Mirror
Having control over the Play Store is the key element to keeping security exploits from being a nightmare, since phone hardware vendors are clearly not ever going to do software updates well. But if you can block the main way seriously bad malware gets onto the system in the first place--installing rogue apps--you can limit the damage.
Samsung has an inescapable problem. If they make their additions to the phone small enough to apply easily to upstream Android, they won't have a distinct enough offering to really distinguish from stock Android. If they modify their platform with a lot of large changes, now they have a hard merge problem as new upstream Android releases come out.
If you are consuming an upstream software distribution, you have to innovate faster than they do in order to produce something really different that is still useful. So far Samsung seems to have navigated that well enough to satisfy customers, with only some complaints about slow upstream merges. But they'll always be facing this problem where serious innovation will fork Google's Android so much that they're stuck with a lot more R&D work to support the result.
The whole reason Android has become successful is that Google has so far done a good job at that task, something no phone hardware vendor was handling before (except Apple). The idea that Samsung will succeed in outperforming Google here, that's an idea that seems to ignore the battered trail of competitors like Nokia, Blackberry, and Motorola. Building a successful phone platform is a much harder problem than any phone hardware manufacturer faces; Google has managed it; and Samsung is going to need a lot of good luck to compete directly at that job.
USB is expected to match current Thunderbolt speeds later this year. Sluggishness updating the USB standard meant Apple got a short period where Thunderbolt was so much faster than anything else around that it enabled some new applications. But currently available 5Gbps USB 3.0 has already closed the important part of that gap, eliminating most of the "couldn't possibly be connected on USB" gap. High resolution outboard video is the only thing really left in that category.
The chunk of the market that needs 4K video processing will still need Thunderbolt speeds, but not other application does. I can't imagine any music software that needs more than 5Gbps, which means the idea of artists and producers walking into a studio can easily happen on USB3 instead. When Apple introduced Thunderbolt, musicians had outgrown USB2, but they're unlikely to ever outgrow USB3. Why would manufacturers of music hardware build anything on Thunderbolt when they can make a cheaper product based on USB3 and sell it into Mac and PC markets?
The main risk is that the split in resources will cause both projects to be not good enough. Being perceived as a downstream version of another project, but with additions incompatible with their terms, that doesn't necessarily favor either end. There's a similar relationship between Debian and Ubuntu that turned out to make both more popular. What LibreOffice is trying to do is more like the XFree86 vs. Xorg split though.
Unfortunately, OpenOffice can't do the reverse without switching their license.
It's not really unfortunate when it's by design. LibreOffice wants to make Apache OpenOffice become so redundant the project just gives up. This is how open source developers protest work that they feel is being done poorly. They fork the project in a way that allows only one-way code copying, and then try to starve the original of resources and its user base.
Time Machine keeps an event store journal of changes, the process is described at How Time Machine Works its Magic. What you're describing might be a "deep scan" pass. It's also possible you're touching a lot of directories with updates, which makes the optimization they apply not as useful.
There are cases where the event store makes Time Machine backups nearly instant, which is never the case for rsync based approaches being complained about here.
Specifically how DRBD handles recovery after an outage of the replication network. The situations where the disk isn't plugged in will look just like the network outage scenario DRBD handles. I'm not sure whether this will be more or less efficiency than the mdadm bitmap approach outlined above, but those are the two main ways people do this specific operation.
It's hilarious how Apple finally dropped Firewire only to adopt Thunderbolt, which might as well be called Firewire 2011. I really like Thunderbolt as a cost no object design, but what the market has proven every single time is that an I/O chipset has to be cheap and easy to license to succeed. USB 3.0 made Thunderbolt obviously obsolete before the first Apple model supporting it shipped.
Can you believe someone thinks this is about "modular, external upgrades"? Replacing on-board Ethernet with the Thunderbolt to Gigabit Ethernet Adapter is one of the most transparent margin increasing cash grabs I've ever seen.
I haven't found much value to "reveal codes" once I started consistently applying style sheets to all text. Micro-managing the codes that go into the document encourages complicated one-off edits, and doing that is where most of the document structure problem I see originated from in the first place. I look at a list of all the styles used in the document, and if there's anything that looks out of place I'll kill it from that viewpoint. That approach converges on a known clean document in way that takes a lot less individual code review work. YMMV, but I'd never go back to staring at formatting codes again now that I've embraced styles.
Why use something as complicated at LaTeX if you don't care about formatting? Use something that looks like plain text until you want to apply formatting, like reST, Markdown, or Asciidoc. Using LaTeX as your example of a non-WYSIWYG editor just scares people off, when they could just \relax and type simple text.
I heard they're going full-on retard with the next name change. Coming soon: GimpOffice!
The history of the US government shows it's willing to use census data for rounding up citizens into internment camps. The ability of Facebook to ruin your life with its data mining is quite trivial in comparison.
Possibly, but there are a lot of tasks that only see about a doubling of speed. A C++ port is only likely to speed things up, while a GPU one is certain to. (Presuming the assumption about parallel execution is correct)
Publisher Heise is a popular and well regarded brand name for tech news in German. The English "The H" was trying to leverage their existing brand reputation. It didn't work out, but I can understand why they tried using that name to try. It's not as bad as the dubious reasoning behind some of the poorly chosen open source project names. (LibreOffice, I'm looking at you too)
The last major Android update applied to Nexus phones was 4.2.2, which rolled out in Februrary. If you haven't gotten an update in six months, something is wrong with your setup. My Nexus phone has also gotten multiple revamps to various Play applications in the last few months, which was most noticeable to me in a complete redesign of the Play Music application. The last update there I know of was a month ago. I'm not certain what form (if any) the fix for this exploit has been pushed to the phones yet--could be a core update or fix in a play app--but your claim that they haven't changed anything recently isn't true.
You know what else used to be a nutball theory? That the NSA had vast spying capabilities being used to monitor large swaths of the Internet all of the time.
There's plenty of historical examples that show lists of citizens meeting some criteria turning into a list of people to inflict government action upon. We don't even have leave the US to find one. It was the US Census database that was used to round up Japanese citizens for internment to fulfill Executive Order 9066. If I have an unusual political belief--let's use the example from the TFA of advocating marijuana--I have every reason to believe that when the government collects data about my communication, it might one day use that to prosecute me for drug related offenses, and launch investigations of those I deal with too. That sort of chilling effect on political speech is why monitoring makes free political speech impossible. Any student of history knows the bad situations that leads to.
If the US government actually cared about the limits on its scope in the constitution, we would not have the Authorization for Use of Military Force Against Terrorists or the Patriot Act. When the government isn't even paying attention to its own rules on declaring war, the idea that the enumerated powers provide any limit on its scope is rather weak. A government that's let all that happen is not going to suddenly turn introspective on the vast subject of whether its recent decisions are really within its powers.
Unlike the ninth, the courts still act like the first amendment is valid sometimes, which is what makes that a better bet for waging a lawsuit.
But why chase after a complicated case involving an obscure amendment when there's a simple one available? Americans generally understand that political speech is protected by the 1st amendment. Point out that monitoring makes that impossible, and you're done, in a way that's very easy to explain to people--and therefore rally support around.
His bone density is going to be lower than someone who lives on Krypton itself. But if all of the structural components to his body, from bone to muscle to neurons, are adapted to be just plain stronger, some of that might be retained even without as much load on your body.
At this point we know just how much things like time in space degrade physical function, suggesting that a body's natural high gravity capability is trumped by recent environment stress. But the high-gravity powered Superman was the one of the 30th through 50's. The shift from a gravity powered hero to the magic yellow sun powers happened during the 60's, partly due to understanding of this area improving so much then. You can almost see how Superman's power explanations evolved in step with early space exploration.
Right, the whole yellow sun thing didn't show up until the silver age era in the early 60's. Before that he was jumping--"able to leap tall buildings in a single bound"--and they modeled the low gravity powers based on speculation about what a man on the moon would be capable of doing.
You kids and your new fangled reboot nonsense. Real fans know Superman can fly because Earth's gravity is lower than Krypton's.
Coffee cups are a really bad example to bring up here. The warnings are there to try and dislodge ideas like the McDonald's coffee lawsuit. The reason that woman won a large judgement against McDonald's is that they were knowingly selling an unsafe product and just didn't care what happened to their customers.
So the problems leading to the warnings were not so much that people were stupid. It was that some number of corporations selling coffee were acting irresponsibly. In a social environment where legal penalties are the only way to add corporate accountability for unsafe behavior, you're kind of stuck with suing them to make a useful change. And when that happens, you can expect that those companies are going to add warnings to try and reduce their liability. That's not really connected to consumers being dumb in the coffee case.
The reason why that's a particularly bad example is that people see that sort of necessary legal action, and then apply it to shifting blame for any problem with a product. The subtle difference is that the McDonald's coffee was unfit for its stated purpose as sold, making it defective by objective measures. You cannot measure anything wrong with an Apple product because it lets you view porn. That's a subjective, moral issue rather than something you can build a factual case around.
Serious Business (TM) users are going to see the boot screen of their Linux distribution. The only people who see Tux at boot right now are ones who will appreciate the joke.
Most of the Windows laptops I look at are using 2 to 3GB of RAM. There is almost zero demand for RAM beyond 4GB among consumers, and that's absolutely correct. You have the cause/effect backwards. The migration to 64 bits wasn't slow because people couldn't get the software. It was slow because the faster hardware didn't help very much, making it impossible to cost justify putting any work into that.
Adding more RAM to machine that is only caching a few GB before a reboot will not increase its speed at all. Speed certainly wouldn't double by having twice as much RAM. The reason why people are spending money on SSD instead of RAM is because memory only helps once you've read data from disk once. There are some small uses of RAM for things like temporary files, but those are not common on consumer workloads either.
Back when all of the mass market machines were dipping into swap to run their normal application, adding RAM made them much faster. And that move was held back a little bit by the 32 bit memory limit. Those days are years in the rear view now though. I upgraded all of my laptops from 8GB to 16GB of RAM recently, and there was no responsiveness improvement for day to day work. I'm just not using more than 8GB very often, unless I get crazy with the number of web browser tabs going at once.
The Jump the Shark episode of the X-Files in 2002 was when Jumping the Shark jumped the shark. That added millions of people who started making these joke badly, and the average quality of such comments has slowly fallen of ever since. The alternate date to pick wasn't much later, which is 2003 when John Hein's book had come out. I thought it was clear we were into the boring repeat phase a little before then.