The Nexus 6P has a known battery problem which does shut off when it hits a lower percentage. I had a 6P and it was annoying, to say the least.
The difference with this story is that this is software and intended, not a bug with a faulty phone/model.
Seems to be that they did, but Varnish didn't suit their needs as they couldn't fit all the data in RAM. It's OK to change what you use because you outgrow it.
The Tube (TFL) are trying to introduce driverless trains. Its the unions that are stopping them.
I'm sure if TFL could get rid of all drivers tomorrow and replace them with driverless trains they would.
The thing that will hold up real deployment of this will be unions rather than the technology.
Maybe 'dead' for personal usage however as part of Google Apps it is a no brainer and integrates nicely with the whole of the Apps suite.
I am prepared to eat my words however I would be extremely surprised if Google kill off Drive for Apps.
That does suck!
I'm not familiar with the law in the USA but in the UK you can be let go for very little within the first 2 years of employment. You don't have a right for unfair dismissal for the first two years.
The notice period is 1 week for anyone that has worked less than 2 years.
There are other benefits than SEO when thinking about guest blogging. Personally I see guest blogging as awareness building first, with any bump in SEO a nice bonus.
I meant startup as a culture not in the terms of funding.
The fact that Google starts and closes down products very frequently is evidence of this.
What about Google X? Isn't that a bit like a startup?
Maybe I meant to say that departments WITHIN Google are run like startups not Google itself.
Even if you have the resources to support something, should you if its not your core focus?
Personal I feel that Google is still run as a startup, which is fantastic however people expect Google to be a corporate company.
Also outside of HN/geek how many people REALLY used Reader? I bet you its less than 0.1% of the overall Google users. I would have done exactly the same in Google's position.
If a feature had been built that only 0.1% of users are using yet is taking up time to run, why keep it?
The problem with hand-holding is how many times have you created good looking prompts to introduce a new feature and then find that the client just clicks through them ignoring what was written?
It took me a while to understand the benefit of IronWorker however a 'server-less' environment is exactly what we need for some small discrete jobs.
I know that these jobs will scale up (in number) without the need to deploy more servers or maintain them.