The same idea was used in a real-world attack. It used to be possible on the Tenex system in the early seventies to recover a password by laying out an attempted password across a page boundary, and observing whether the checker incurred a page fault.
The bug was that you could align the given password string so that it was at the end of a page boundary, and have the next page in the address space mapped to a non-existant page of a write-protected file. Normally, Tenex would create a page when you tried to access a non-existant page, but in this case it couldn't (since the file was write-protected).
So, you did a password-checking system call (e.g. the system call which tried to obtain owner access to another directory) set up in this way and you would get one of two failures: Incorrect Password meant that your prefix was wrong, Page Fault meant that your prefix was right but that you need more characters.
Apple, unlike Microsoft, is well-positioned to take advantage of demise of high-tech industry as we know it. This demise has already happened once, with an industry that was "hi-tech" for centuries: clocks and watches.
It means that as you move functionality (not data) between the server and the client, you need to rewrite your code. For example if you do input validation, you need to write the same code twice: once in {Java, Python, Ruby} or whatever the server side language is, and the second time in JavaScript so you can alert the user that the data in some fields doesn't pass the checks.
This is not a problem if you are using GWT, or if you do serverside programming in JavaScript.
Complete results: http://icpc.baylor.edu/worldfinals/results
UC Berkeley placed highest in North America, beating MIT, CMU, Harvard and Stanford.