I think there are two click mechanics going on -> visual and non visual. Depending on the level, not every click gives you visual feedback of the liquid decreasing, however, you get audio feedback for every click. Would be better if the clicks were always registered visually, though, and should be easy for the developer to implement.
Today's race was the first time we got to see just how fast the Mercedes is on low fuel with new tires. This innovation is worth 2 seconds per lap, which is massive in this sport. The championship is theirs to lose this year. Teams don't make up such a time gap over a season, and Mercedes won't stop developing.
In the UK Amazon has its own parcel delivery service that is used to deliver the majority of the larger parcels in my area. But it's not great. Some of the drivers decide they don't have time, or it's near the end of their shift, and log deliveries as no one home. I've had this confirmed by some of the drivers that do bother delivering.
So while I've been home all day, I get an email (usually around 6pm) claiming no one was in when they attempted the delivery.
This is frustrating when it happens once, but it has now become a regular occurrence and complaints just end in a free month of Prime being added to my account (had 4 extensions this year so far).
If you live north of Perth in Scotland and a parcel is sent via one of the big couriers it often gets subcontracted out to a local courier or franchised operator who can add another two to three days to deliver something that should be next day. I used to live in Perth and never had a single Prime delivery arrived next day as promised - in one ridiculous example, they shipped a parcel from their Greenock fulfilment centre to Perth and it took a week to arrive!. I ended up getting half the money back and cancelling Prime.
Four years later I found myself eligible for the free trial and have given Prime another shot, so far so good with 3 out of 3 orders arriving next day via Royal Mail.
"Some of the drivers decide they don't have time, or it's near the end of their shift, and log deliveries as no one home" - yes that is truly annoying and verging on fraudulent behaviour.
I don't believe that to be the case, at least not any more. The lead devs are quite active on Twitter, they have a bug reporting system all users can take advantage of, the documentations is growing, and the DRM you speak of is no longer in place and they admitted it was a bad decision (after the skulls incident).
It's becoming a very solid toolset that can produce games for most platforms and does not require a plug-in for web games. The recent roll out of v1.2 has also made it much faster.
Mike Dailly, head of development at YoYo recently did an AMA on Reddit. There's some good information in there on the state of GM and its future.
"I reached out to play support via email, and here is the response I got: "We're aware of a streaming issue with the Google Play All Access app and the Nexus Q and are working on a fix""
"Chrome was compromised using similar methods to the IE10 and Firefox attacks. MWR Labs bypassed Chrome’s sandbox and used a Windows kernel vulnerability in Windows 7 to elevate privileges as well as execute commands outside of the sandbox. In addition to executing code, MWR researchers were able to read memory and find the base addresses of certain .DLL files."
As one of the owners of the Chrome Windows sandbox, that level of inaccuracy hurts to read. The correct statement is that Nils and Jon's pwn2own exploit bypassed the sandbox by using a Windows kernel vulnerability that's exposed in every process on the system. You can argue about the extent to which you should be able to rely on the kernel to enforce its guarantees, but the component that failed isn't a point of debate.
