1. Continued income from it (people aren't going to continue to buy it if the bad reviews keep coming in).
2. You keep/improve your reputation. If your software isn't working well for any reason at all, it can give a bad reputation to the person/company attached.
3. You increase the chances of a good buy-out in the future, over what it would currently bring now.
We all know it can be difficult to get traction on a project, not to mention paying users. You already have proved this one can get both.
I actually think high level questions like these are just conversation starters which can get into highly technical conversations quickly.
Sort of like the technologies themselves; GameCenter and CoreEverything are abstractions of lower level functionality.
Being able to discuss their purpose, how to use them, and how to glue them together is what a good developer is. The rest is just syntax.
I think part of the idea of interview questions like these is that it will get a developer into those finer points, if they are in a technical discussion.
1/I often discover new things and have new thoughts and ideas along the way of an implementation which hadn't presented themselves previously.
2/I think it's a great way to avoid overthinking a feature or arguing too much for or against it. If nearing a majority consensus (with oneself or team) and there is time to spare, add it to Version 2 -- advantages being point #1 above, and having it prepared should it be deemed worthy to be merged to Version 1. I've heard that having features in the chamber ready to release is something big corps commonly do.
"After conducting an initial background check of a candidate for employment, USIS was required to perform a second review to make sure no important details had been missed. From 2008 through 2011, USIS allegedly skipped this second review in up to 50 percent of the cases. But it conveyed to federal officials that these reviews had, in fact, been performed."[0]
Other than the obvious-- Snowden turned out to do what he did, Altegrity allegedly made other mistakes, which the submitted article didn't mention.
To be fair, filling out a form for a sandwich is about 5% of the food service operation at Google.
Most are just like lunchrooms in school, with much better food. Sorry that someone didn't give you a better experience there, with regards to food and otherwise.
I totally agree web site and web app are used interchangeably sometimes -- I was just answering the op as to how I and many people I know classify them and their differences as they relate to the topic of the article, javascript.
2012 MBP retina with 8gb ram here..
Major performance issues with Chrome -- when videos are playing in tabs, 10+ tabs open, etc.
Systems Preferences are the least of the problems I've came across.