Not quite. The attack is easily extensible so that the attackers can "run before" the target app at any time by simply deleting the keychain entry and recreating it with a new ACL that permits the target app and themselves access to the entry. From the user's perspective, they see an unexplained repeat prompt to enter their password which they'll gladly do and from there on, the attackers have access to the password.

These security holes are quite awful.

Anywhere that latency is not adequately met by "cloud apps" will require desktop apps.

Over time, bandwidth will become less of an issue as it continues to improve but latency is governed by the speed of light and light ain't getting any faster.

Conversely, if a "cloud app" is a huge pile of JavaScript that does everything locally on your machine, it is arguable that it is really a desktop app.

This is the beginning of Microsoft creating a competing ecosystem on Android. At some point in the not so distant future it will be entirely feasible for an Android manufacturer to dump Google's software stack in favor of Microsoft's. Unlike Samsung and many other handset manufacturers, Microsoft has the know how and capability to create and maintain a viable alternative to Google's ecosystem.

Roll your own app on an old iPhone/iPod/iPad. Use iOS's triple home button press (aka Guided Access - http://support.apple.com/en-us...) to lock the iDevice to the one app.

That button press can do anything from sending an e-mail to a tweet to your own custom web service (automatic SMS and phone calls are out if you stick to official iOS APIs).

Learn to read.

Mechanical watches were so ridiculously convenient and useful that people would gladly wind their watches once a day. Similarly, if the Apple Watch proves convenient and useful, people will gladly charge it once a day.

Of course, the most myopic aspect of these articles is the unwritten presumption that today's state of the art will never improve. Yes, Apple Watch will need to be charged once a day for the next couple of years, but charge times are going to improve tremendously as Moore's Law continues to plug along. The Apple Watch will improve in a way analogous to the way mechanical and later quartz watches improved far beyond the limitations of the original pocket watches and wristwatches.

Most feel they can hand wave through their technical interviews by citing some abstraction that while possibly correct doesn't actually solve the problem presented. If you are interviewing for a software position, hand waving doesn't write code.
Many others feel the technical questions are beneath them and refuse to answer very basic questions that are used to simply weed out the vast sea of know nothings.

If you fall into either of these camps, you have a problem. Your response to the STL question hints you may be suffering from the latter problem.

The question about the STL containers is not "overly technical". It's just stupid.

I currently have a retired iPhone 4s serving primarily as a git server. Also useful as an SSH tunnel into the home network; to view IP cameras remotely without exposing them to the outside world, for example.

The 4s replaced a 3Gs that replaced a 3G that replaced a long serving, flash only, nslu2 running CVS and later SVN.

Of the bunch, the 4s is the first device that is indistinguishable over the network, performance wise, from PC workstations I've worked with. I imagine the 5, 5s and 6/6+ must be fantastic.

It is available, compact, mobile, has a built in screen and keyboard, and 24 hour UPS battery backup with plenty of oomph and storage for a git server and much more. What's not to love?

De-coupling code is great. However, code refactoring should have no detrimental effects on end user experience. If it does, you are doing it wrong.

Your explanation implies a tail wagging the dog.

The reason this relic still exists is likely explained at 0:41 into the video where you can see the words "Iron Mountain" above the entrance. What can be processed with a few low power computers in a rack for a few hundred dollars a year is generating a mountain of cash for Iron Mountain in rental and consulting "fees".

Follow the money.

All your friend's music and movies are already there.

It is not a coincidence that Tesla has no dealerships. It likely never will.

This strong-arming is a perfect example for the reason. Dealerships wield in an inordinate amount of political power in their regions. The result hash been that once a manufacturer grants a dealership license to a dealership in a certain area, it is perpetual, geographically exclusive and irrevocable by the manufacturer. Unheard of conditions in practically any other business.

Tesla will sooner open its own dealerships across Ohio's state lines. The lost sales taxes will eventually prove irresistible to the coin operated legislature.

The comparison is inappropriate.

At the same time, I do understand the disgust with the neo-luddites of SF and their alarming witch hunt - it is a mob.

There are two basic approaches to handle this:

http://marshallbrain.com/manna1.htm