Python and Ruby have been GPL from the beginning, unlike Java. I think that makes reimplementation of the API certainly legal, since using the code directly is legal as well. The "end of programming as we know it" seems like a stretch - maybe the "end of Java as we know it". Or am I missing something here?

Actually last year it was a Galaxy Tab 10.1 (not a XOOM), a ChromeBook with 2 years free 3G, and a Verizon 4G hotspot with 3 months of free service for everyone; and for some attending certain sessions, an Xperia and an Adruino ADK.

I created a machine that was featured on the Google Developer's Google+ stream, and I did not get a ticket (nor even an early invitation code).

WIth 6,250 queries *per* *second* when registration opened at 7AM, it's not the least bit surprising not everyone who wanted a ticket got one: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fplus.google.com%2F107117483540235115863%2Fposts%2Fiyc4arLjidR

i.e., the few thousand tickets available could have theoretically been sold out in seconds. The Moscone Center West would not even have the capacity for 25K+ Google employees, let alone the 10's of thousands of developers/students who would like to attend. My only point here is that there's a lot of demand and very little supply, so there's going to be a lot of disappointed people. I don't think a better registration system, programming challenges, doubling capacity, a lottery, etc will do much to placate everyone who wants a ticket. Perhaps the only sensible way to reduce demand would to be double, triple, or quadruple the price.

FWIW, I've been in 2009 and 2011 - in my experience, it's mostly engineers, developers and others interested in and actively working on Google technology - not people there for just for the freebies (although they are certainly welcomed).

The UDID is really useful for collecting analytics, such as with Flurry Analytics. You can really easily get nice graphs and charts on how users in aggregate are using your app, or drill down to any particular (anyonymous) user based on the UDID. For these analytics to be useful, you need to specify some type of unique identifier for the device. A UDID makes perfect sense, and there really isn't any standard or easy way to map the UDID to any particular user anyway, so it's hard to see what all the fuss is about. Regardless, the app should let the user know the UDID is being logged, and allow them the option to turn the logging off.