As an aside, I expect anti-drone systems to become a significant debate soon enough (e.g. if there's a drone peeping in my windows, what rights do I have to disable it?), and then to become a significant commercial concern.
2,015 karma · joined April 2, 2014
As an aside, I expect anti-drone systems to become a significant debate soon enough (e.g. if there's a drone peeping in my windows, what rights do I have to disable it?), and then to become a significant commercial concern.
You mean exactly like the EMV that is on every Canadian credit card since about 2007? NFC / Chip hold unique tokens that have on device cryptography, exactly as you've described. You can't "steal" anything of consequence via NFC or the chip, and that's why it was designed. Further while you say that it's for the vendor, the liable party for fraud is actually the credit card companies, which is exactly why they made EMV.
You seem to think this is all new because of EMVCo, however it is a standardization for the last mile: Google Wallet originally was doing what the credit cards themselves do, holding the secret key and identifiers on an NXP secure element. There are issues with that (largely carrier related) which is why the industry started moving to software-held tokens, as in the Apple solution. Presenting an iPhone token offers zero additional security over presenting a Canadian chip or NFC credit card, and that notion is rather ridiculous.
Credit (and debit) cards in Canada and elsewhere have had NFC functionality for several years now. You never hand your card or numbers to anyone, but instead through chip insertion or proximal NFC it communicates with the identifier on the card, which the payment processor can correlate with you, and using the secret on the card cryptographically signs a transaction.
The most secure way I can use my credit card...is to use my credit card: Nothing that can be usurped is passed to the POS terminal.
Apple is essentially injecting themselves in a simple process that works extremely well.
Further the nuclear industry is one with a very poor track record of promises versus delivery. The cheap power, for instance, tends to turn into expensive power when plants need to be refurbished at mind-boggling costs (such as here in Ontario where we've gone from the cheapest power in North America, courtesy of huge hydroelectric benefits, to one of the most expensive because of our nuclear legacy). And the waste issue remains a significant issue.
Nuclear was a great alternative to fossil fuels. It is a very poor alternative to alternatives (wind, solar, geothermal, hydroelectric, etc), and simply increasing energy efficiency.
If you fail to get the basic context of a thread, maybe the internet isn't for you.
http://mobilesemi.blogspot.ca/2014/09/apples-64-bit-processo...
By Oct. 2012, Samsung had licensed the A53 and A57 core designs: http://www.techhive.com/article/2013298/arm-introduces-64bit.... . They didn't have 'many details'; they had the design itself.
ARM designs are like a GIT repository, and the AXX continued having revisions and changes through 2013. Running with it early and you are bound to either go on a detour or end up with a noncompetitive variant.
No it wasn't. A57 wasn't actually done when Apple outed Cyclone. Apple clearly ran with early aspects of A57 (your disingenuous misreading about ARMv8 being ignored). At exactly the same timeframe, nvidia, Qualcomm, and others had as many details of A57 and ARMv8, and none of them ran with it. Indeed, nvidia and Qualcomm are just getting to 64-bit parts, doing a pretty good job with their existing architectures.
Apple wanted to be first, and they pounded every bit out of 64-bits in their marketing. But here, again, we have to pretend that reality isn't as it actually is.
Also, it's clear that they DON'T try all that hard; they could have used the six-core variant of the PowerVR used here, at the cost of battery life
This is absurdity theater. Apple has chosen higher bin/tier PowerVR parts than her peers for virtually every single generation. But because they didn't choose even higher we are to believe that they don't try hard? Do you actually look at the benchmarks, or just continue on with a ridiculous narrative based upon preconceived notions?
Apple makes a really big deal about their cores and GPU, as they have every right to (they're pretty great). Quite aside from their keynotes that focus extensively on this, on the product page you learn, right near the top, about the A8 64-bit processor and M8 coprocessor, as if these facts have any relevance to an end user. They're bragging points. Apple talks about their 64-bit advantage ad nauseam.
They absolutely brag about their chip. They boast specs (as they boast "retina" displays and thinness and grams and materials).
This is surprisingly ignorant from Anandtech. Surely they know better.
While Apple raced to win the spec war (I say that tongue in cheek, but the truth is that Apple tries really hard to give you bragging rights, buying the biggest PowerVR designs, jumping on incomplete ARM specs, etc), going to ARMv8 far before her peers by creating a derivative of early A57 designs (much like Qualcomm did with Krait, getting in early on the new A15 design), every other vendor has been soberly pursuing ARM A57 at their own pace: It isn't like there is some great lack of performance in competing devices, and this simply isn't a critical thing, so there seems to be no great rush.
The Tegra K1 Denver will be the first salvo from alternatives, and early indications are that it will provide pretty extraordinary performance, and presumably we'll search for ways of using that power productively.
Looks like I've stepped into the distortion field, where Apple is both uncatchably ahead of everyone, and simultaneously not even trying.
Be sure to log into your alt now. I have a feeling you go through accounts to evade hellbannings.
Go is absolutely preferred by people building real solutions to real problems. Pure, idealized languages like Haskell seem to be preferred by people who don't actually do anything with it, but instead talk about it. It is the "big brother" language.
I don't mean this dismissively, though it invariably sounds that way, but there is a huge divide between things that actually get things done, and things that you can debate the intricacies of for weeks on end while you foment that grand plan that you'll never actually pursue.
Though I will add that your nonsensical, ignorant simplification and mischaracterization of Go merely belies the fact that you have virtually no real knowledge of it at all, beyond probably some rubbed off "knowledge" from advocacy boards.
Early evangelism for Mongodb was overwhelmingly one that hyped performance over all others. It was, somewhat infamously now, webscale.
So now pgsql (since 9.2, but vastly improved in 9.3) can also do the things that MongoDB does, better, if you want to do the document approach (which is a serious debate unto itself). That is news and is interesting.
As for scaling out, I would argue that 9.3 offers more realistic, robust options than MongoDB does.
The people who have no knowledge or skill in Go, on the other hand, fill the message boards, railing rabidly about how absolutely critical generics are, and don't these people (who almost universally have extensive experience across a number of languages) know what they're missing?
Google makes no bones about continually recording your location history, and they certainly don't need Ingress for that. They use the location history for predicatively estimating your trips, etc.
FWIW, quite a few apps realized that they could actually change the 16 color palette multiple times during each line scan. Spectrum 512 famously used this to allow for, as the name suggests, 512 colors simultaneously.
It can be a very specific cut of meat. A less common herb (fresh). "Ethnic" spices. A distinct type of dairy (which can be simply something like whole milk. I rarely use this, and never buy it in a normal shopping trip), such as a unique type of cheese. A strange vegetable. A very specific oil (even something like peanut or sesame oil would be odd in a normal house, though the moment you open it the expiry clock starts ticking). Etc. And if I do buy them, I usually have to buy them in such a quantity that it makes the meal very expensive, because I know the end result is that I throw out 9/10ths of it, having used the small amount in the recipe.
I usually just skip the recipe, not trusting my judgment on potential substitutions. In the odd case I do pursue it, the shopping experience is usually time consuming and brutal, and very expensive, to make one meal.
There is a business, or at least social, model somewhere in this. e.g. a "menu club" where everyone works through the recipes of a Jamie Oliver book, ideally in a more sustainable manner -- e.g. everyone stops by a location with their own containers and takes the right quantity from the bulk and economically purchased ingredients, taking a little vial of peanut oil, an eggplant, three anchovies, and on and on.
The trend is towards a comfortable size, beyond which thinness stopped being a big selling point. The Galaxy S5, for example, is thicker than the Galaxy S4. The Note 4 is thicker than the Note 3.
Contrary to common notions, Apple occasionally chases specs, and the thin and light thing seems to be one of them (just as unobtanium type materials often make a big presence in Apple devices -- material specs -- regardless of suitability for purpose).
Apple makes fantastic devices, but just as some other manufacturers chase irrelevant things like octal core processors and truly absurd pixel densities, Apple does the same "not for your benefit, but for our bragging" pursuits.
They wanted a larger phone, for sure, but I think one would reasonably assume structural stability for a $1000 consumer device (often bought under a pay-as-you-go loan courtesy of carrier subsidization) under fairly normal conditions.
Further this isn't "sitting on it" -- the issues seem to be coming via seemingly innocuous, but longer term, flexing in front pockets. Aluminum is not all or nothing, and will quite happily give slowly and gradually over hours.
Maybe it's all overblown -- these things tend to be on new Apple releases -- but I don't see how some can so quickly resort to blame the customer antics.
It is a brand new, $1000 consumer device. As haughty and rich as we all present ourselves, it really supremely sucks if you're the person whose brand new device got bent -- regardless of your available spending cash, it's a major bummer, moreso if you have a 2 year contract ahead of you and a dead device. That is why there is a "hysteria".
Gorilla glass (not sure if the iPhone uses that brand specifically, but they use ion enhanced glass which is what it is) famously bends.
This story got knocked back to page 3 for having too many comments to upvotes, as an aside.
Based upon, apparently, your opinion?
they are built to be durable in a way that very few of their competitors are.
Material porn has absolutely nothing to do with actual suitability to purpose. iPhone devices are absolutely wonderful devices, but the narrative around the build materials, which people wrongly conflate with built "quality", is detached from reality.