E-mail uses push notifications, you make it sound like it's on a 30 minute polling interval but that's simply not the case - it's nearly instant, certainly every bit as fast as on Android. Twitter does the same thing. Just read the documentation if you don't want to take my word for it. Using polling for any kind of instant messaging is not something you want to do since it's massively inefficient, much better to let the server tell you when there's something new to fetch.

As for porting, what you are describing is the same on every platform. You have an iOS app and want to port it to Android? Better brush up on those Java skills because your ObjC is worthless there. You can theoretically use C/C++ as a lowest common denominator between the two but almost nobody does that except possibly for some very core functionality and then you have to write a ton of platform-specific wrappers for the device-dependent stuff anyway. Oh and the UI, which is probably the most time-consuming single part of your app if you want to get it right.

I will give you this - being the minority platform, WP7 certainly stands more to lose from not sharing a common language with Android/iOS than the other way around. I don't really want WP7 apps that are just least-effort ports of Android apps though, and if you're as concerned about battery life as you say then you should find the thought of porting over a big fat VM just to run a few more apps abhorrent. It's not like porting is that hard, and unlike Android, WP7 is actually fun to code for. I've put one app on the market already and am working on a second. Never could muster up the energy to do that for Android, well not on my spare time anyway, there's just too much pomp and ceremony required to get anything done. I do code for Android at work though, since they're paying me well to put up with it. :)

Strange, I seem to have no trouble receiving mail while I'm doing other things on my WP7. Perhaps because the "extremely limited means" are actually quite sufficient. I believe limiting multitasking a bit is a tradeoff for better battery life, and that's certainly fine by me. Apps like navigation and music players (Spotify, Nokia Music) seem to have no trouble whatsoever with me switching to a different app and back. The web browser dutifully remembers which tabs I had open. So no, not a big deal at all. The Skype limitation I believe is a beta issue.

C/C++ support is probably coming eventually but - are you kidding me? Lack of a Java runtime an impediment? C# is by far a nicer language to program in, and is instantly accessible to any Java developer (being basically Java++ by design). Lack of Java support doesn't seem to have particularly hurt Apple in their quest for global mobile domination. The only possible use I can see for Java on WP7 would be to make porting of Android apps easier but they would feel right out of place on WP7 anyway since it has a very different UI.

Not really true anymore. I've had a Lumia 800 since november and the only two things I'm really missing now is a native app for Google+ (though the mobile web version works fine) and something that can talk to the OBD2 Bluetooth dongle I have for my car. Not exactly your Angry Birds of smartphone apps. Also, a lot of the WP7 apps feel more polished than their Android versions. The Facebook app for instance.

Maybe this varies from country to country, but here in Sweden, the decimeter, deciliter, centimeter and centiliter, hectogram (typically just called "hecto" for short) are used very frequently and you would have a hard time finding anyone over the age of 7 who doesn't have an intuitive understanding of them.

However, we pretty much never use "deca" and "hectoliter" is very rare, though most people know what they are.

This article stinks on so many levels. It is well-known that Nokia had an internal war going on for years around the Symbian platform, resulting in, among other things, the well-designed but effectively DOA Nokia N9 which in effect became the prototype for the Lumia 800. Maybe Meego would have gone on to be a market-leading platform, but it got buried by politics. Clearly this guy was on the losing team and now he's trying to use whatever authority he still thinks he has to trash-talk Nokia.

Yet the very first comment on his blog post is proof that Nokia is far from dead. No, market share for Windows Phone 7 isn't that great, but it's obviously growing at a rapid rate, and even if it never passes Android or iOS - there's plenty of room in the market for a third player. Blackberry was it for years until they shit the bed.

What the world most certainly doesn't need is yet another Android phone manufacturer. We already have more than enough. Microsoft had the cash that Nokia needed and an OS that, while not perfect, is certainly a differentiator. Couple this with Nokia's design sense and you get a phone which stands out in the sea of blandness (and the fact that the Lumia 800 alone now accounts for something like 85% of all WinPhone7 sales in the EU is evidence of this).

I don't want to go too much into subjective opinion here, but my own experiences with the Lumia 800 is that it is a damn good phone and a pleasure to develop for. It performs much better than its meager specs would suggest. It is certainly proving popular in my circle of friends, almost all of which owned high-end Android phones before. Thanks to the apparent ease of porting stuff from Xbox, there is a ton of great games for it. And it's being marketed VERY competently - certainly better than any Android phone I've seen except possibly Samsung's. I have a very hard time believing it will flop.

However - and this is important - even if I'm wrong, Microsoft can easily afford not to have Windows Phone 7 be an instant success. They are swimming in money. And so can Nokia, because they are feeding off Microsoft. It's happened before with the Xbox, the same Xbox that got laughed at and is now making enough money that Microsoft can afford to keep going at the smartphone business until they succeed.

Quite the opposite. Macs ship with the biggest piece of bloatware there is, and it's quite hard to get rid of. It's called Mac OS X.

Try something like Steam where buying and installing a game is something like four clicks (one to select the game, one to click install, one to confirm the payment information and one to start the game). They have quite a few "classic" games as well, updated to run on the latest version of Windows with sound and graphics.

The grandparent was making a claim ("Does anyone really like Microsoft, other than those who swear by their products and services? I really doubt it.") trivially disproved by example, so I thought an anecdote appropriate. I have never doubted that there exists people who really don't use Windows at all - in fact I know some of those as well, but this was not relevant to my point, which was solely to point out that there are, in fact, computer geeks who use Windows by choice.

Does anyone really like Microsoft, other than those who swear by their products and services? I really doubt it. Most users just seem to be forced to put up with it and are either ignorant of other options or afraid of trying something unfamiliar.

I have used Linux, BSD, MacOS (X) and Solaris but my home computers (laptop, gaming PC, two servers) all run Windows, because it gets things done and I haven't had a BSOD or a serious issue with it for years. Finding drivers or apps is never a problem because everyone develops for Windows first, Mac OS X second, Linux probably never or perhaps a distant third.

Being a geek most of my friends are as well and Windows is still by far the most common OS on their home PCs. One guy bought a shiny MBP and promptly installed Windows on it. Pretty much everyone who runs Linux dual-boots with Windows. So yes, when given a choice, even very computer-literate people will freely choose Windows. Because it gets things done, doesn't crash and has drivers for everything. Simple as that.

My phone runs Android, though.

Sadly traps like these are a time-honoured ingredient in adventure games... you reminded me of this ancient E2 node, well worth a read. http://everything2.com/title/King%2527s+Quest+5+design+flaw

You chose to wear that leash, don't complain if it doesn't fit.

I have a desk job with a computer and e-mail. I have a cellphone with my work e-mail so I can stay updated while I'm not in the office, but I only really read it while I'm working. I guess if something really important came up my boss could call me in, and I'd be happy to oblige if I could because I know I would be compensated for it. So far this hasn't ever happened, though. My work weeks are 40 hours, although I feel no need to keep track of every minute - sometimes I leave a bit early, sometimes late. My boss doesn't really mind when I leave so long as work gets done on time. There's no punch clock where I work.

You may claim that my situation is unique and that I've been very lucky but this has been the same for the last three places I've worked in. I only left those jobs because I wanted better pay and more interesting things to do. The same goes for pretty much everyone I know. If you find yourself "leashed" to work, your cellphone or your boss's whims, switch employers. There are plenty - PLENTY - out there that care about keeping their employees happy. It has nothing to do with technology.

I wonder if this is simply a more expensive version of ReadyBoost. Similarly, it takes your most frequently used files and puts them on a flash drive for faster access times, in a way that is transparent to the end user. In this case I wonder if there would be any speed gain from using this on a PC running Windows 7 with ReadyBoost? Caching always introduces some overhead, so rather than using multiple levels of "flash cache" it might be better to simply turn ReadyBoost off in that case. My experience with ReadyBoost has been that it does indeed improve performance, but in no way close to using a real SSD as the system drive.

Windows Mobile does not have a backwards/forwards compatibility problem with desktop Windows because both run .NET. The GUI parts are different in places but you don't want to re-use those anyways as a desktop UI looks and works like crap on a mobile device. For the most part, though - and certainly including such basic bits as color management - .NET on the desktop is a perfect superset of .NET Compact Framework on Windows Mobile. Furthermore, the docs neatly outline what is available in CF and what isn't. At one of my previous jobs we used to literally compile the exact same (non-GUI) C# code for Windows Mobile and Windows XP/Vista. Only very few #ifdefs were required.

Now that Microsoft is going with Windows Phone 7, where apps will apparently be entirely Silverlight-based, I am guessing compatibility will be even better. Imaging building a web/desktop app in Silverlight/WPF and then changing the compiler flags to make an app that runs locally on any Windows Phone 7. No #ifdefs in sight. Nobody else has anything close to that level of portability between desktop/mobile except maybe Adobe.

Of course. Every PC hardware site worth a penny does regular articles on which CPU is currently the fastest and which will give you the most for your money. As well as comparisons between Intel/AMD. My favorite site for such things is Tom's Hardware, though Google will likely find you many more.

Which CPU is actually fastest heavily depends on what you will be using it for. Your list of "regular geek activities" does not narrow it down enough. Also, many applications contain optimizations that target a particular CPU family or architecture.

CPU articles: http://www.tomshardware.co.uk/review/Components,1/CPU,1/

Best (gaming) CPU for the money as of dec 09: http://www.tomshardware.co.uk/best-gaming-cpu,review-31755.html

All CPU performance charts: http://www.tomshardware.co.uk/charts/processors,6.html