https://developers.google.com/events/io/help#reg_tips "We'll take you to a waiting page while we try to find you a ticket. Expect to be on this page for up to six minutes. On this page, don't refresh your browser or your ticket search will restart."
I believe that's new for this year. 2011 was a total mess as the registration page was just a ColdFusion site run by their event management vendor, and they were clearly used to medical conferences and the like that don't get the same swift response that I/O would get. The registration site served up way more 503 errors than pages.
Last year was better because Google took it in-house, but it was still an F5-fest.
I don't get it... He's trying to solve the problem of typing text in a touch device... with an XBox controller? why not better carry a small keyboard?
The program looks awesome, but i believe it would be more productive to have this features on a regular IDE where you can actually use the keyboard... All the movement between nodes looks terrific.
He has RSI from using the keyboard, so making the editor work with a controller first makes sense because he is the only person using his program at the moment.
He developed carpal tunnel or some other wrist aliment, and can't type for any real amount of time on a keyboard, apparently using an xbox controller is easier but really he wants to move to using the kinect.
We're using it for all our toolchain in our small first game. We've also created a small build system based on v8 (javascript), but integrated it using go, it generates all your project so you just need to compile it.
We were using it also for our web page (a custom blog engine made on go), but, we left it on alpha, and Go 1 changed a lot, gofix didn't fixed and priorities made us choose another tool for our web page.
Still, i think go only needs a desktop GUI toolkit to become popular. It has a lot of potential.
Previous years have been this way? is this new?