...if you're a fan of late 70s/early 80s computer culture.

Somebody gave me Steven Levy's Hackers: Heroes of the Computer Revolution as a teen (thankfully missing the minefield of shitty books with the term "hacker" in their title) and it was amazing. Early days computer hobbyists, Paul Allen and Bill Gates writing BASIC for the Altair on a timeshare and dealing with the hobbyists who wanted to copy it instead of buy it, Ken and Roberta Williams and Sierra On-Line, and so much more.

Also loved the more recent Commodore: A Company on the Edge by Brian Bagnall. Just captivates the imagination to read about people hand-drawing their CPUs. There's an enthusiasm in the early computer industry that seems to have dampened over the years, as startups and corporations begin with the money in mind rather than the starry-eyed idealism and hobbyist tendencies that powered the first personal computer businesses.

Neither of these feature Ashton Kutcher, however, or even Steve Jobs to any great extent. But if your passion for computers is in their function rather than their form I highly recommend the above books.

This scene came after the bit where Jobs signed The Beatles, and before he wrote the software that made the special effects in the original Star Wars trilogy possible.

This has been known in the industry for some time, and has always been considered something of a too-simple solution to a too-complex problem.

The workaround to increase the complexity of stack smashing in this regard is in ASLR/FMA, address space layout randomization with fuzzy memory allocation. Basically, reduce the predictability of memory locations from memory-fill attacks by causing memory allocation (in hardware, transparent to the OS) to return slightly more or less than what is called for. This has some implications for programmers to be sure; for example, for malloc(), if you think you'll need 1000 bytes, you just call for 1500 to make sure you get enough back from the OS to work with.

For this trivial increase in workload, fuzzy memory allocation means that all the same memory allocations that go on in the system will add up to different amounts of memory used at different times, making it improbable at best that guessing offsets will be successful in the future. And we can all agree this is only a good thing when most people are already running with 8GB or more.

Have you looked into the feasibility of creating a slingshot that could fire smaller slingshots that, in turn, could perhaps fire something smaller themselves?

(from their developer documentation)

MEGA supports secure cross-account access to folders. The owner of the folder is solely responsible for managing access; shares are non-transitive. All participants in a shared folder gain cryptographic access through a common share-specific key, which is passed from the owner (theoretically, from anyone participating in the share, but this would create a significant security risk in the event of a compromise of the core infrastructure) to new participants through RSA. All keys of the nodes in a shared folder, including its root node, are encrypted to this share key.

So, you and some friends share a folder you can all upload to. If two of you happen to upload the same content within the folder, MEGA's servers can deduplicate that because the content will be encrypted (client side) with the same key and can be compared. On the other hand, if you each upload the same content into your private space, the two copies would not look the same in encrypted form and couldn't be deduplicated.

However, it is not safe IMHO to trust encryption that's outside your control. But somebody will hack together MEGA's API with client-side encryption, and the pirates won't use it because they won't think it's worth the bother.

Could muddle it in a different direction and wonder why taxes are being spent on something people have to pay for.

But for some reason, the very smartest guppies had no interest in swimming at all but would just hang around the bottom of the tank, head side down.

For example, nothing was said about GOTOs being liberally sprinkled throughout the code. If he's working in a non-optimal language that doesn't support GOTO, he should try hacking in the functionality with preprocessor defines. Maybe even hack in a preprocessor if the language designer forgot one, or add another preprocessor if not. With a few stacked preprocessors one can even write his own (better) computer language, and what seasoned programmer doesn't aspire to have one or two of those under his belt?

Also among the business practices Google has agreed to stop is 'scraping Web content from rivals and allegedly passing it off as its own, said FTC Chairman Jon Leibowitz.'"

So, would there be a problem if Google scraped Web content from rivals and proudly proclaimed it was passing it off as its own?

I was thinking of this in terms of ICANN's UDRP, not American libel or trademark law.

She has a great industry reputation and everyone that knows her loves her.

That's what matters. Maybe she can trademark her name and seize the domain as being confusingly similar, but it's still throwing time and attention at somebody who clearly craves it, for dubious gain.