> 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

> 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? 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.