Africans. Blackberry is the single best-selling brand of smartphone in South Africa, and the second-best-selling (after Nokia) brand of cellphones cellphones in general.

That's wrong. You're taking a half a sentence and quoting it out of context. Clause 3(b) doesn't require you to do anything - it gives you the option of doing that. Clause 3(a) permits you instead to provide the source code only to those to whom you sell (or give) the compiled binaries. 3(c) is yet another option, but it's availably strictly for non-commercial distribution so it doesn't apply here.

He is well within his rights to ask you to buy his product before he gives you the source code.

I'd like it to be Koeksister. Unfortunately, I'm told that they are planning to use Key Lime Pie. (It's not a biggie, but I'm not keen on that as a name).

I don't think anyone's calling out THQ - they made an amazing offer. The complaints are specifically toward Humble specifically for going back on the very things for which fans were most impressed with them. I'm not too happy about that myself, but I'm sure that they didn't take the decision to do this lightly. THQ - an excellent developer and publisher - is having problems right now, and Humble chose to burn a bit of their ample supply of good karma to help them. It means we can get some THQ games cheaply now and hopefully boost THQ enough that they can continue making games in the future.

No, the Linux Foundation. And no, it doesn't mean they'll release a binary without source code - it just means that the binary presented for signing must not be licensed as GLPv3 (or similar, whatever that means).

Killer whales have no self respect? :(

Sufficiency is not necessity, so listing a few examples of unrelated potential fair uses isn't much of an argument. And nobody here is using children as a defense - the EFF is suing Universal, not the other way around. Universal is being accused of abusing the DMCA takedown process, and the defense is that one of their songs happened to appear incidentally in the background to a 29-second video of a baby acting cute.

Naturally, the trick to doing minimalism right is to use as little of it as possible.

Can you provide a citation for those numbers? TFA links here, which lists Galaxy SIII and Galaxy Nexus at 1560 and 1039 respectively.

Oh, IE certainly is a game. A strange game. The only winning move is not to play.

I once received a cheque for a million Gummiberries, but it bounced.

</badjoke>

I remember that. It actually was all true, and not as you describe. They never said that the memory usage was "a feature, not a bug". That would be daft. They said that the enormous memory usage of one particular version wasn't caused by a memory leak as many suspected (there were several known ones at that stage, but this wasn't one of them), but rather that it was caused by a new feature that was added to that version and removed from the next (hey, let's use all the free memory as a cache pool! when apps need more memory we'll feed it to them as needed. what could go wrong?). It was a misfeature - a bad idea that worked as it was designed to.

Triggering a separate interrupt for individual characters was the slow way of rendering text. There's the overhead of the IRQ jump itself, handling cursor movement, window wrapping, scrolling - all that is OK if done once for a batch of characters but too much work when repeated for each character. Most programs used DOS or BIOS calls to print out strings of text at a time. Those occasional programs that had need to twiddle random characters on the screen would edit segment $B800 directly. Whether using BIOS, DOS or the text buffer, you're still using text mode. And believe me - it was much faster just setting the byte for a character and letting the hardware figure it out than plotting the pixels for the text in software. That's what text mode was - hardware-accelerated graphics that increased speed and reduced memory usage at the expense of limiting you to a set of pre-defined characters always arranged in a grid. There weren't compatibility issues because the protocol (the location and format of the text buffer in segment $B800) was kept sufficiently consistent from CGA to EGA to VGA.

"Copyright 2004–2006 TextDrive Inc. TextDrive is a trademark of Joyent Inc."

It looks to me like the agreement was with Joyent the whole time. At the very least they were a party to the agreement. Joyent still exists.

A market that likes to overpay is a good market to be in :) There's a question about how long that tendency will last, but it's been going strong for over 3 years so far and doesn't appear to be slowing yet. It possibly won't until games are so commonplace on that platform that users no longer feel the need to encourage growth, but at that stage you will probably no longer have your problem of a limited userbase.