I regularly use both GoToMeeting and Join.me for international online meetings. I don't have a preference; both work very well to coordinate our activities over. The presenter's screen is displayed for all to see. Voice can be via your microphone or dial in for those who don't have a microphone on their PC.

One thing I've noticed about the curved screen is that at least some part of it will have glare. I can generally arrange a flat screen such that light sources in the room will not have glare in my normal seating locations. The curved screen will always have some part of it that is at the correct angle for the lights or windows to glare off it. You can see this in the store displays too.

While I absolutely oppose inserting a backdoor into any security, this case is a bit different in that the owner of the phone also wants the security hacked. I have no problem with that, as a one-off hack for the owner

While I absolutely oppose inserting a backdoor into any security, this case is a bit different in that the owner of the phone also wants the security hacked. I have no problem with that, as a one-off hack. Most of us use company resources for personal (email for instance), but I don't pretend that anything that touches a company server is private. It's spelled out in company policy. the same applies to a company phone. All those records and content belong to the company. If an employee is stupid enough to give private information to the company, it's on them.

The US tried something similar back in the 90's, but was slightly smarter about it. Anyone remember the clipper chip? This inexpensive chip was to be installed in phones, PCs, anywhere "secure" encryption was needed. It also provided for key escrow so that any authorized government entity could obtain the key. It never did catch on, and the public backlash resulted in several free public encryption schemes including PGP, which is still in use.

It boils down to business philosophy. Your point about the company depending on developers providing lots of apps is valid. Traditionally MS has been eager to encourage developers. Recent management has been more interested in bottom line and paying out dividends. When short term goals like revenue become more important than long term growth, this is what you get. From a pure revenue perspective, there is a 'sweet spot' in the demand/price curve. Everyone knows that when price is low, sales go up. High prices yield fewer sales. Revenue is the product of sales and revenue; there is an ideal price at which the sales * price product is maximized. This price change may be an attempt to find that sweet spot.

I haven't broken any keyboards, but I have worn some of the letters off the keys. Being a touch typist, it doesn't bother me in the least. The IT guys have tried to replace it several times. I won't let them, since my kb is ergonomic and I'm used to it. Besides, I consider it a badge of honor and enjoy their consternation when they can't hunt and peck. :)

I buy MSDN for one reason: To get all the OS versions I need for platform testing. I have to certify software on the 3 most recent OS versions in English, French, German, Spanish, and Traditional Chinese. I occasionally have to test on other systems as well, when bug reports come in from other countries. It's useful that the subscription comes with the latest VS releases, and OS release candidates that I can do "heads up" testing on. I think the knowlegebase sucks. I do better on a general web search to find solutions for problems.

I need to choose the most appropriate data engine for an application, and can use some advice. Background: I am replacing an existing application, rewriting it from ground up using VS 2010, C# and .NET 4.0. The prior app used Access style databases. Microsoft discourages this type of database for new apps, or I would continue with it. Very few of our customers need or use database servers. Typically, a customer would maintain a collection of separate databases, one for each project. Databases only need to be accessed locally. The self contained single file approach of the Access database was ideal, since it is highly portable and easily archived or deleted after a project ends. The largest database I have ever seen reached 100 mb. Typical databases are less than 20 mb, many around 2-4 mb. The data model is largely relational, and idealy suited to object modeling (without inherited classes). I like the EF and Code First options in VS 2010, but it all seems to be focused on working with a single server based db. I need to be able to browse and open databases. In rare cases, a customer may even open more than one db at a time, using mdi children for each db. This is not an absolute requirement, but is highly desirable. Any ideas or suggestions?