Additionally, and as it mentioned in the article linked, implementing screenshot functionality is non-trivial to do it well with respect to other possible features. E.g. Users of Exchange IRM are long familiar with their lack of being able to take screenshots or copy text from IRM-protected emails and there are likely a number of other scenarios that need to be considered when implementing a "simple" feature like screenshots.

"It seems clear that Microsoft do not regard easy screen capture as a high priority for WP7"-- it's not "seems" if it was said right in the interview.

This was not an ad. It was a teaser shown before a "Lawrence of Arabia" Secret Cinema showing in London. http://www.secretcinema.org/windowsphone/

Source: http://www.engadget.com/2011/01/07/ford-unveils-f...

Those who rely on news delivered at CES will probably never even hear of “Chet Logothestian.” =)

Joe Belfiore is a VP for Windows Phone and he’s visibly passionate and technical enough that he resonates with geeks (see also, Steven Sinofsky). But having him take on overall messaging for Three Screens and a Cloud would be glossing over the challenges of Windows Phone and the other mentioned products above; challenges which are unique to each product’s area and require focused attention. I'd believe the best messaging around 3S&C happens as a result of good execution of all relevent portions working with each other.

Basic differences in release processes: 1) Web-services only need to update a set of servers to roll out changes for millions of users whereas mobile-clients like WP7 must be updated on millions of different devices. 2) Web-services control the hardware they release their code on whereas WP7 must be tested on a growing number of handsets with different networks.

I’d rather see any software development team (for any product) use a reasonable amount of time to iron out (test) fixes and feature improvements than trade test coverage to release updates sooner. The damage done by a bad update outstrips any benefit gained by a rushed release, especially for a new product/brand like WP7. Also, having Facebook go down due to a bad update is arguably less critical than having your phone bug out when you need it most due to a bad update.