Can you use something simple like the group version of Lastpass / setup their accounts and manage their passwords / revoke access?

Over the last few days the public has gained an unusually detailed insight into how hard Google will fight to protect its users against government overreaching, even when this involves only a single user's data.

What are those insights?!?!?

"A 10th of the speed doesn't matter if it is 100th the price..."

I'd think that it starts mattering when you run out of time (think of order volumes over XMAS .. ). There are only so many robots you can deploy, given the size of a warehouse.

There you go - YouTube video of the iHerb "vending machine"... pretty cool to it work - skip to around 1:18 to see the "vending machine" ... watch the whole thing to see how optimising the packing, before it gets stocked helps speed things up.

I think the future of massive warehouses will involve RFIDs and standardised packaging. Products are packed far too randomly ... if standard packages were deployed, robots dexterity could perhaps be reduced?

I am sure there is a very significant technical challenge getting those awesome aircraft back in the air and more importantly getting them back on the ground safely. However, the link is pure and simple link bait and an extremely low quality rehash of the official website.

I assumed coming from a publication like Network World, there would be some geekery in the article... but was left sadly disappointed.

I wish I could mod you up. Spot on ...

I very seriously agree ... but as a small "community" business, we do need an app or two to allow our users to connect with our websites. Simple things like push messaging to send them notifications, lean data delivery (no need to deliver entire html pages for every pageview) etc etc.

So, the choice is - do we choose a single hybrid framework and learn that, or do we develop for IOS / Android / Windows phones natively and learn three things?

In terms of frameworks etc.. .as long as we can communicate to a PHP / MySQL driven back end, which spits out JSON / XML - the front end can be redone over some time. I think...

I think it is important enough to have atleast one 'skunk-works' type project that every developer needs to work on, just to keep up with what will be boring a year or two down the road.

I avoided "not boring" for a couple of years and for the last month, while I look at hybrid mobile apps, I am stunned by my lack of knowledge and the abundance of terms, concepts and technologies that mean nothing to me ... angular, ionic, grunt, promises, JSX, reactjs, compass, gulp, firebase... the list could go on and on and on, these are just things I've started researching over the last few weeks, to make sure I make the right choice.

Every organisation needs a "not boring" slot of time for their developers. Not for product that needs to ship NOW.. but for stuff that may need to ship next year.

May I suggest that you go back in time (or go into the future) and look for a video called "EPIC" or "Googlezon".

A lot of this is possible with crowdsourcing, but use machine driven processes for the basics - far too many agendas out there once your site / service becomes popular. Look at text / sentiment analysis engines and mashups with larger public databases to drive facts.

Not just "sounds like"... they've got nothing other than speculation which confirms earlier speculation.

Tschauner’s description of bridgmanite gives us no such insights about the inside of the Earth, other than to confirm what scientists believed to have been true for quite some time: The mineral exists, and it can occur naturally under highly pressurized conditions.

Seems like submissions from certain accounts (MojoKid is one of them) get approved, regardless of the value to the community. I'd speculate that sites like hothardware do advertorials which they then promote through various "social networks".

I seriously recommend this blog from Rackspace to those who are so caught up in cloudy-cluster-off-premises-corporate talk.

This rising complexity and cost on the multi-tenant cloud is hitting customers in four main ways:
- They spend more on engineering time and talent to architect for failure on the multi-tenant cloud, which is complex and hard.
- They also spend more on engineering to deal with inconsistent performance, which is even harder.
- They spend more on infrastructure, because over-provisioning is one of the major ways to compensate for inconsistent performance.
- They spend more through the virtualization tax, which can diminish disk and network performance by 5 percent to 20 percent.

KEEP your existing hardware as a live back up for when it starts raining in the cloud. Better yet, build in cost for new hardware on your rack over the next year to lower costs / maintenance and get some experience in building and operating your own in-house cloudy thing.

To be technically correct, the character would be called, "Wonder Peroffspring" :)

Thank you. Now that summary would have given me a lot more incentive to read the linked article. Was a bit put of by the nail polish bit -- simply because as much as I know that IBM maintains a very diverse range of research teams, nail polish would not have been something their geeks or PR department would have highlighted. :)