"Scope creep", singular? So there's only one person at the NSA looking at us with a periscope? As long as he's not putting it in Uranus....

girlintraining is only one person, so I'm not sure why you're using the plural "ones" here.

Only if you use a Trojan.

GCD might be cutting-edge, but it does not itself make Mavericks a cutting-edge version of OS X, given that it dates back to Snow Leopard, and it doesn't belong in a list whose other members are features new in Mavericks. In the list "interrupt coalescing, memory compression, grand central dispatch, app nap.", at least one of these things is not like the others, as the saying goes, and, if by "interrupt coalescing" you mean "timer coalescing", exactly one of those things is not like the others.

(As for "interrupt coalescing", I have no reason to believe that, for example, jerbun's comment in this Gizmodo story:

My best guess is that they are essentially doing this:
Interrupt Coalescing
This taken from the "Time Coalescing" statement from which I am making the assumption that they really mean "Interrupt Coalescing."
The basic idea is that instead of waking up the processor every single time some sort of I/O needs to be done by a peripheral, they let some of them wait a little longer. Not all I/O is latency dependent, and as such the wake-up time can be postponed. This means that a series of interrupts can be handled all at once, and then the processor can go back to sleep.

More in depth explanation:
Anandtech on Haswell 6/10/13 5:21pm

is a good guess.

I'm more inclined to go with Apple's own description of it in their "OS X Mavericks Core Technologies Overview" document, which indicates that it shifts the times of events scheduled to happen sufficiently close together in time so that, instead of happening at a time as close as possible to the scheduled time, they happen at times further from their scheduled time in a fashion that allows more of them to be handled within one timer-based wakeup. One consequence of this might be that fewer timer interrupts occur (as I remember, XNU was made tickless at least as far back as Lion, so there aren't periodic timer interrupts), but that particular bit of interrupt coalescing - it only concerns timer interrupts - isn't the main goal, and is arguably not a goal at all, just a side-effect of reducing the number of timer-based wakeups from sleep.)

If you haven't, here's where they sell refurbished equipment, and, yes, selling refurbished Macs, at least, predated Jobs's death.

At least for Calendar and Address Book^W^WContacts, both are fixed in Mavericks.

It wasn't enough for my Snow Leopard MBP (admittedly, a zillion Safari windows, occasional firing up of various VMware Fusion VMs to do libpcap and/or Wireshark development work, and native development work on libpcap/tcpdump/Wireshark isn't exactly a typical load), and isn't enough for the other Snow Leopard MBP in the household (no development work or Fusion, but somewhere between .1 and .5 zillion Safari windows, and occasional Chrome windows on sites where Chrome sucks less than Safari - I'm looking at you, mlslistings.com).

Yes, it'll set them above all other vendors in terms of "spending time and energy on a small group of users who will probably not contribute enough to their bottom like to make the investment make sense". Anybody who cares about CP/M apps, for example, should go get a copy of CP/M if they don't have one already and an emulator for a Z80-based PC and solve their problem that way, not expect Apple or Microsoft or any other OS vendor to care.

Well, "made"; their Web site says "all 500 units sold".

Presumably you're either referring to changes to GCD or expanding the use of GCD, given that GCD first appeared in OS X in Snow Leopard.

So what does he have to do with anything called "Mavericks"?

Apparently you missed the target of the snark in this thread.

So, speaking of Sweden, how does it compare with Germany and the US on those issues?

Yeah. He's really half human, half alien lizard.

Neither necessary nor sufficient.

Wrong.