Windows Server 2016, not likely to arrive until the second half of next year, is going to shake up the way Microsoft licenses its server operating system, moving away from per socket licensing to per core. The change was first spotted by Wes Miller who is, for his sins, an expert on Microsoft licensing policies.

Windows Server 2012 introduced a great rationalization in the way Microsoft licensed its server operating system. The two main editions, Standard and Datacenter, had identical features, and differed only in terms of the number of virtual operating system instances they supported. Standard supported two VMs (in addition to the host OS); Datacenter was unlimited. Beyond that, they were identical. The licenses for both editions were sold in two socket units; one license was needed for each pair of sockets a system contained.

Windows Server 2016 makes that simple system less simple. First, it reinstates the functional differences between Standard and Datacenter editions. Datacenter will include additional storage replication capabilities, a new network stack with richer virtualization options, and shielded virtual machines that protect the content of a virtual machine from the administrator of the host operating system. These features won't be found in the Standard edition.

Recently, there has been a lot of discussion about the current state of Apple's software quality. Anyone with even a passing familiarity with development knows that bugs are par for the course, and most people aren't bothered by small, day-to-day bugs that are fixed within a reasonable timeframe. Obviously, like everyone else, Apple's software has its share of those.

But there's another category of bug—glaring, perplexing bugs that couldn't possibly have escaped the attention of the software engineers in question, let alone the quality assurance department. Such issues exist, and sometimes they go unfixed for months. Or years. Or ever. Hopefully, the set of network issues with OS X 10.10 described below won't fall into this column, but they do raise an obvious question: why?

For 12 years, the mDNSResponder service managed a surprisingly large part of our Mac's networking, and it managed this task well. But as of OS X 10.10, the mDNSResponder has been replaced with discoveryd, which does the same thing. Mostly. Here are some strange networking problems we've observed since installing 10.10: