By that standard Google Chrome itself has been malware for years - many pieces of software have bundled it in exchange for money from Google and made it hard not to accidentally install it, including I think Java, Flash, and various more shady products, and Google hasn't given a fuck.
Barring another bug, it can - and probably does - scan for *all* ways to exploit it. The issue is that Android itself doesn't properly verify the certificate chain in packages before installing them, and Play Services can easily perform all of the missing checks itself and reject any package that fails them.
Unfortunately, some common routers contain a buggy early revision of the QCA9880 802.11ac chip that's not supported by ath10k and never will be.
It's a Red Queen's Race though - no matter how far everyone is willing to go to achieve the American Dream, only a tiny proportion of them ever will, and meanwhile all the rest are stuck running as fast as they can just to stay exactly where they are.
How much do you pay for Maps updates with Apple? Presumably, the amount it costs to buying a new iDevice every time they stop supporting the old one, plus the cost of a data connection... which is quite a bit.
The money laundering, and possibly also some of the other crimes, was committed in the US by American subsidiaries that Mark Karpeles set up specifically for that purpose.
Last time I heard, CVS sold homeopathic remedies too, along with most of the other major supermarkets and pharmacy chains in the US. Does that mean that all their medicines and "healthy" foods are just marketing to the credulous too?
For values of "debunked" equal to "people clueless about how VAC works are loudly insisting that it's not true, and being believed because Valve fanbois". (Amongst other issues, you won't find the code of any VAC modules in Steam's or the game's DLLs because they're downloaded from the server at runtime in order to make them harder to reverse-engineer and block.) Someone later in the thread has apparently tested and found that stuffing the DNS cache with bogus entries increases the amount of SSL-encrypted data VAC sends back by almost exactly twice the size of the MD5 hashes of all those entries, and clearing the cache returns the amount of data sent back to what it was. (It may not necessarily be possible for others to replicate this, as I recall one of VAC's anti-reverse-engineering measures is that different people receive a different subset of the payload modules. So far no-one's tried though, they've just said it's not proof enough.)
You've forgotten about fixed point, which isn't really any more complicated to implement than integer arithmetic and is a perfectly reasonable way of implementing integer division by a fixed divisor. (A lot of compilers actually use this trick, because even running on a CPU it's often more efficient than using hardware division.)
Yeah, and nearly all of the professional applications people are going to be running on this cannot make use of the second GPU. Not even slightly. Literally the only reason to get dual GPUs is if you're buying from Apple and don't have any choice in the matter.
Yeah, quite. The base Mac Pro actually turns out to be fairly reasonably priced for the combination of components inside, but - and this is important - there is essentially no reason to get that combination of components unless you have no other choice because you're buying a Mac. For instance, they're paying out quite a bit of extra money in order to fit everything into a smaller case, even though that'd actually be a downside for many customers. Also, most of the professional applications out there that use GPU acceleration can only make use of a single GPU, so the second $3400 GPU will be sitting completely idle for most Mac Pro buyers. What's more, as the article mentions many apps run better on NVidia GPUs anyway. Also, how many of the GPU-accelerated apps can also make full use of a 12-core CPU?
Running 20 year old Linux binaries is certainly possible too - I think one or two of the kernel devs do it from time to time but it requires a kernel option that's not always enabled and old versions of libraries.
Why? Running glorified PR pieces is the safest thing you can do under British libel law. Also, it certainly didn't stop our journalists going off the rails and smearing random members of the public on the front page, since random members of the public don't have the money for a libel suit - it just blocked criticism of large businesses and the wealthy.
Except they didn't notify their customers when the potential backdoor became public knowledge and most crypto library developers cautioned against it. That happened a year or two after it was introduced back in 2006 or 2007, yet they didn't notify their customers or change it from being the default until 2013, leaving those customers using crypto that RSA basically knew was backdoored for years. (It should've been even more obvious to RSA that there was a backdoor than it was to the rest of the crypto community, since the people with the ability to backdoor it had bribed them to use it as the default in their crypto product.)
Not really. Laws for war make sense, even though only the winning side can enforce them directly, because by forcing the winning side to pin down the rules by which they consider the losers war criminals we give the press a tool to shame anyone on that side who broke those rules.