What I find mind-blowing, though, is that Intel's new architecture Haswell which will come out mid 2013, and is supposed to be even more GPU-oriented than previous chips, will only support OpenGL 3.2, which will be 4 years old by the time the chip launches (some sources say OpenGL 4.0 - still 3 years old though)...and yet it will support DirectX 11.1. I find that incredibly disappointing.
I guess Intel just doesn't care about OpenGL. I'm not sure how they are supposed to make us believe that they are serious about entering the mobile market with that kind of attitude towards OpenGL.
They've publicly stated that the hardware is OpenGL 4 capable. (Google it.)
Bingo. Microsoft was never very fond of the idea of people porting Windows apps to other platforms. If people develop portable apps that run everywhere, the network effects achieved by having OEMs bundling Windows on every PC are neutralized.
(Note, i'm actually a little excited about the Surface tablet as a potential device that crosses the chasm between full tablet and laptop. But I don't have very many apps that I use now on my iPad.)
EDIT: Also, I don't know much about any game development SDK engines that abstract devs from these proprietary libraries and runtimes...however I think they must exist?
I have a Transformer Prime (#2, Transformer Infinity is the newest one) and the keyboard dock. Android apps/games, plus terminal, VNC, etc for doing real work.
And Android 4.0 looks more like Windows 7 than Windows 8 does (black "taskbar" on the bottom with clock and notifications on the right, home button, back button, and app switcher button on the left, and the 'desktop' can have icons and widgets).
That is not a reason to not code and offer a code wrapper for BSD-sockets-like API based on WinRT sockets.
Of course, no need to cover 100% of the API and they could use lots of warnings to force developers to slow transition.
Oh, the irony. If you actually look at those #ifdefs, the vast majority of them are #ifdef __WIN32__ - because Microsoft didn't really care about compatibility when they first adopted BSD code. Compared to Unix/Windows, the differences between BSD and Linux are almost nonexistent.
Re: networking, you are of course right. At the same time, I can sympathize with Microsoft's decision to abandon Winsock. Cross-platform use of BSD sockets is mired in a deplorable mess of #defines and '90s incompatibilities. For new code, the non-blocking WinRT API is a million times better -- the question is, what can Microsoft do to make porting easier?
[1] http://code.google.com/p/angleproject/