Depends what he wants to play. Sim racing could work, as it's mostly foot control with some arm movement for the wheel. Can be done with one arm and one leg if need be.
Better cross-platform support. In my experience .NET works fine in Mono anyway, so by extension F# is likely fine on Linux/OSX, but your mileage may vary.
I find this an interesting, common, conceptual misunderstanding.
When somebody asks this question, he always thinks this way:
- I have a system "A" with x GB of ram, with y GB of swap.
- I have a system "B" with x+y GB of ram, and no swap, because it has all the virtual memory A is using.
well, the problem is that one should not compare system B with system A, he should compare system B with system C:
- I have a system "C", with x+y GB of ram, and z of swap.
system C will perform potentially better than B.
The generic explanation is that the kernel may decide that it's better to swap out some data, and use the space for caching purposes. This is a concept, that within limits, it's not related to the amount of RAM.
As long as 'z' is not proportional to x or y that might be fine. If you consider 'z' as a percentage of your RAM then you'll notice that your expensive server with lots of RAM
is way slower than a cheap one with small RAM and smaller swap, just because it takes less time for the kernel to fill the swap and finally kill the offending process.
I'd allocate swap on the order of how much RAM your applications use. So if they need 2 GB of RAM to be comfortable, 1-4 GB of swap will give them room to be paged out when necessary. In most situations disk space is cheap, so erring on the side of too much won't hurt.
Reductions in public services/welfare supposedly matched by temporary levies on high earners. Those levies will be gone soon enough and the high earners will make back any shortfall through super changes anyway.
Apple will adjust pricing based on currency. If the Australian currency is getting weaker it may be because the emerging markets that it depends on are seeing turmoil in their currencies because of the prospect of Fed QE tapering.
Apple has overcharged both in Australia and Europe for decades, even when the currency has been strong. It's simply because they believe that people who live there will stomach a larger price. It's probably true. It's still infuriating.
It results in funny cases where a Nexus 4 can be 1/3 the price of an iPhone 5.
Just fly up to Hong Kong over a holiday and buy an iPhone there. Prices are cheap, and its what we used to do in Mainland China before (now, iPhone pricing is about 20% higher than the USA sticker, which probably mostly due to VAT).
1) 64-bit has bigger overhead. If you have, for example, 8 GB maximum (e.g. a notebook) then you'll have the advantage of having more RAM available by using 32-bit system. If you just use a notebook for surfing, you wouldn't care. If you did something that had specific memory needs, it was the best solution before the notebooks with more RAM possible appeared.
2) Other hardware compatibility as there is still enough hardware without 64-bit drivers. But don't expect too much there: some kind of such hardware will have problem with this patch though. You'd have to try to be sure.
Now that even notebooks allow 16 GB the patch is becoming less relevant.
1/If you have 8 GiB of RAM, and you just surf, you don't care about the 64-bit overhead. Also 64-bit is more convenient as browser tend to flirt with the 2/3 GiB process limit.
2/If you have 64-bit machine, this problem is unlikely to exist on Windows.
Opera Mini has a proxy server it uses to compress data before it reaches your device. This is extremely useful when using mobile data because it's both faster and cheaper. (At least, in Australia, where mobile Internet is both slow and expensive)
