inversionOf

A sleeping core is obviously the most efficient core, however you have said nothing to discount what I said. Putting a core to sleep is a very costly activity, which is exactly why it happens at the millisecond scale.

Before that happens, the core will likely have been frequency scaled to more appropriately fit the window's loading. I mean, we know this is the case right now, and that "run fast and go to sleep" is not the primary policy. It's "run as fast as appropriate for the workload to fill a quantum, and sleep when there is no workload". There are many if not most workloads that are externally bound, or event triggered enough that sleep is completely out of the question and running faster does nothing.

Your words have been used (out of context and inappropriately) to bolster DannyBee when they represent, literally, all that is wrong with Hacker News.

Yes. You do. If I'm casually browsing non-intensive web pages, e-reading, or watching a Netflix movie, or even encoding a video, the background is doing IO rate limited system updates and basic data logging, etc, the vast majority of the time the CPU demands are very low, but frequent enough that putting a CPU to sleep is completely out of the question.

An A53 has a much lower ceiling, but a much better middle tier power usage level, than the A57. Yes, if you want to run a benchmark the A53 is not a good bet (and is generally worse in a workload power usage), but it is a very good bet for most real world usage.

As a Nexus 5 user I'm pleased with most of the changes and non-changes. 2GB is fine for a smartphone, and an image sensor with more than double the light capture area per pixel is brilliant, and if it delivers the better photographs will be worth it right there. Losing OIS...I don't think that's a downgrade as OIS was always suspect to begin with (not least because OIS only helps for lateral movements. It does nothing for rotational movements, and of course make subjects stand still. It yielded a tonne of unusable photos).

The only thing I'm really displeased about is the removal of wireless charging. That was a really nice feature.

Between the Snapdragon 810 and 808, the only real items of concern is that the 808 does not have h265 hardware encoding (the 810 does), and its image processing DSP is 12-bit per pixel rather than the 14-bpp of the 810.

SD storage has always been a mess on Android because it was originally added just as an easy way to port music and movies over. It was essentially supposed to be read-only memory. Then of course apps and users started using it and the ugly, messy history is notorious.

Apple sort of presented it like the App Store is picking and choosing, but it's the enhancements to Xcode that actually enable the functionality. Google could add some tooling improvements to make it slightly easier, but really they've already done all of the hard parts.

Expansion files were a hack, and remain a hack. They are necessary for large games obviously, but really 100MB encompasses the enormous bulk of apps with ease. It would be ideal if Google simply abolished expansion files and folded the sizing into normal APKs.

It is absolutely enabled. It is absolutely working. There is no conspiracy about this. It is one of the reasons most updates take hours to propagate.

You complained about managing thin binaries, so I don't see how the developer managing that would improve anything, not to mention that it adds difficulties to cryptographic signing and verification.

Android updates have been incremental updates for three years now (introduced at the 2012 I/O, and immediately enabled). Your point on that is confused in any case -- why can't it do delta updates (it does...), and why can't the developer do it, but also why does the developer have to do it? You're incredibly complaining about a situation you invented.

And larger APKs are a problem because now the ridiculously easy tools that Google already provides (generating thin binaries for varied targets is extraordinarily simple. A bug regarding expansion files...what is the point of even linking that?) will somehow be unused?

Your post is a very poorly informed rant. I have no idea how it sits on the top.

There is an enormous financial black hole that is just as vulnerable to inspection as simply depositing $1,000,000 in cash in your account. The whole point of money laundering is not only to legitimize the output, it's to make the sources untraceable and arguably viable as well.

The components of a transaction, particularly for the sales of goods, cannot simply appear out of nowhere, or they've done absolutely nothing in the way of money laundering. The people who will ever care about this (the ones who money laundering is constructed to fool) aren't so naive, and if you're selling 100,000 hard drives to justify your income, they're going to ask where you got the hard drives, and demand a financial trail.

Cash businesses that have little variable costs outside of manpower (such as carwashes, laundrymats, even some small restaurants, or selling small crafts on Etsy) are absolutely lucrative tools for money laundering, and can only really get caught if put under heavy scrutiny (e.g. car wash with 10 cars over the week claims revenue of $100,000). As are casinos, and Vegas was built on money laundering -- there are few checks on how much you spend, so whether you spent $1,000,000 in unexplained cash to leave with $950,000 in legitimate winnings, or $10 in legitimate cash to leave with $950,000 in legitimate winnings, it's almost impossible to prove.

There are many, many financial vehicles that are used for money laundering, including life insurance. Selling hard drives on Amazon is not one of them.

http://ask.cars.com/2012/11/why-do-some-volkswagen-diesels-u...

VW claimed to have a trick that removed the need for it on their smaller, lighter cars. But that trick was a trick that only allowed them to pass EPA tests.

The NOx problems were mostly resolved through the injection of urea into exhaust gases (e.g. AdBlue), dramatically reducing NOx emissions while leaving the efficiency and power unaffected. Urea systems add an extra cost and complexity to the vehicle though (not to mention that you need to top up your urea additive occasionally), and VW seemed to find a loophole that allowed them to make small, inexpensive cars without urea injection. They did this by injecting fuel into the exhaust in the absence of Urea, but to achieve the same effect. But this can gunk up the NOx trap if used endlessly (it is far less precise than urea, obviously), reduces fuel economy, etc, so they built this One Little Trick that only actually does that during identified tests.

The primary revenue source of many of these sites are ad clicks (impressions often don't matter). If the function paying the bills are ad clicks, and site stickiness really isn't a thing anymore (nowadays we're all directed by social news, Facebook, etc. Few of us visit specific sites), why not abuse the users that do come by.

A principal web design facet in the past was the notion that you pre-size all of the elements, such that the content layout is static. This basic facet has largely disappeared -- despite being monumentally simple -- and the only rational explanation is that moving content is profitable.

And for sure it is a terrible long term strategy. But the problem is that it's a tragedy of the commons -- your ad payout on most networks is based upon the group norms, not on your own site norms. So if everyone else is click tricking users, your own per click payment drops, so the only viable solution is to join the race to the bottom.

For what? I can only speak for myself but my immediate reaction is to click back and feel annoyed, and consider ad blocker options. It has never led to engagement or a purchase. Ever. The end result is that the performance of ads simply collapses, and sites have to get even trickier to entice accidental clicks. Rinse and repeat.

If you work in the "trick click" space, you are just dooming yourself. It is a race to the bottom.

GM is in no universe blameless, but considerations that hold it like murder are irrational.

VW actively and intentionally misled consumers and regulators to sell cars promising mileage and power levels they don't actually achieve without actually cheating the system. They sold hundreds of thousands of cars -- at the cost of significant air pollution (some 200,000 Americans, and millions worldwide, are estimated to die from air pollution yearly) -- based upon these essentially lies. They actively promoted their eco-friendliness, and their great fuel economy, neither of which are actually true in concert.

http://www.androidcentral.com/list-devices-stagefright-patch...

The vendors and carriers are getting pretty good about this, and the bulk of popular devices get patches surprisingly quickly.

My post above is completely accurate. The moral grandstanding is an embarrassment, and it's worse how well this noise works on HN.

I find this sentiment, and the moderation supporting it, incredible and almost a demonstration of the Stockholm Syndrome.

The anticipation about adblockers on iOS has been fervent and growing for a while now. Marco went and setup an agreement with one of the larger purveyors of block lists, then utilizing that to all advantages to corner the market. I find it highly dubious that he didn't think it would be lucrative.

The ramifications and gray area of adblocking are not new. They are not unknown. This has been a discussion for literally years. As with others, it seems obvious that there is something else that motivated this sudden change of perception, and personally I would wager that very shortly we'll see Ghostery skip the middle man and release their own blocker, probably with some financial considerations.

This is like kicking kittens and then announcing to the world that you're going to stop kicking kittens. Then why kick kittens in the first place?

No one made Marco create an ad blocking app. No one demanded his coordination with Ghostery. No one demanded that he announce it with great fanfare on his site. Moralizing about him stopping it ignores that it was just a few short days ago that he started it.

And now he deserves accolades for stopping it? This is an incredible discussion. Countless other people with the ability and the means, who actually had convictions about this topic, didn't create ad blockers (much less for personal reward). Others still, who have convictions that favor ad blockers, did and stand by their moral compass. Either groups are in a far better position than Arment's "have it both ways" perspective.

So he went all in on something that was already hugely controversial (for weeks regarding iOS, and for years on other platforms). That adblockers would be controversial was blatantly obvious to any of this Earth, and should not be a surprise to anyone.

The world didn't need Marco to get in the ad blocking business. Yet he did in a big way, with a big partnership, and put a big amount of his namespace and reputation behind it.

People infer motives because the notion that this all came as some big surprise rings hollow.

As you said, there is nothing particularly offensive about what the person said (it certainly doesn't seem to be homophobia. It doesn't discount it at all, but by itself is essentially nothing). If it was made into some tense, awkward situation, well that's on everyone involved.

Having said that, everyone should avoid those sorts of statements, however benign, because under the lens of reconsideration, where people are looking for a narrative, it's easy to make them look much worse than intended.

By definition, snapshot isolation is supposed to guarantee that all reads are the consistent, committed data as of the begin transaction, and the commit will fail and rollback if any data altered within a snapshot isolation transaction was already changed. The response by Percona, unless I am reading it wrong, actually agrees that they are not truly implementing snapshot isolation. They then argue that the tester should have tested something totally different, but that doesn't address the snapshot isolation not actually being snapshot isolation.

As to locks, snapshot isolation/MVCC are there to avoid a sea of locks. The solution to a broken snapshot isolation level isn't simply to manually and programmatically demand locks. While that may work, it completely undermines the whole reason for SI.

Those that remain will eventually move to a model where ads come from the site itself, intermixed with content in such a way that makes blocking virtually impossible. This obviously presents trust issues for ad networks, but it really is the only workable solution.

without even spending a dime

Ads wouldn't work if people never spent a dime. This has been going on for quite some time, so the notion that it's built on nothing -- just a bunch of foolish advertisers giving money for nothing -- has always been folly.

People like eating at the park. There are no current food options there. I can "disrupt" the park food business by wheeling my bbq down there and selling burgers (ignore the countless food safety, tax and regulatory issues, or the zoning/garbage/park use policies that led to the park not having food options). Disruption!

EDIT: Actually, why bother having the capital costs of BBQs, fuel logistics and safety liability, etc. Instead I'll just make an app ("Ubbq") and allow providers to register as park hamburger sellers, taking my skim off the top. Disruption!

allowing consumers to use better alternatives and challenging local authorities on their backwards ways

This is a profoundly naive way of viewing what they're doing.

It is live on most devices, and reflects pressure quite accurately, and is doing it by measuring the touch area per contact on the screen, which with a human finger varies based upon the force of the press. Presumably on the Huawei they would just use the actual pressure sensor instead of the proxied size.

http://www.engadget.com/2010/04/08/jobs-if-you-see-a-stylus-...

He specifically refers to the iPad in the actual quote. Anyone claiming otherwise is simply wrong or a revisionist, though such sorts seep out of the woodwork whenever Apple cedes prior claims, rephrasing and adding unspoken criteria to somehow make it prescient and relevant, seen throughout this discussion.

Companies like Uber and AirBnB (and countless others) simply pretend that those complexities don't exist -- the market to be disrupted only because they're willing to completely circumvent laws and standards -- and money starts falling on their heads.

I've done high performance nginx, in the million request per second range (there are situations that benefit from these, though unfortunately such discussions always get waylaid by people insisting that performance doesn't matter), but there is enormous system overhead at this rate that I'd like to get around.