36 comments

[ 0.23 ms ] story [ 58.7 ms ] thread
I'd say there are way too many slides about I/O swag (!) in the I/O extended organizer guide. It gives a hopefully wrong impression that there was too much thought put into swag.
Be sure to click the equalizer control icon and run the webgl and web audio experiment. (might be chrome only)
It ran in Firefox, and then froze my browser :(

Edit: Oh, working fine now. I should mention I'm running the Developer Edition (which used to be Aurora), two versions ahead of "current" Firefox. 37.0a2

Doesn't seem to work in Firefox for me..

EDIT: The reason was that I had web components enabled.

>Chrome Experiment Ahead

There a thread earlier today on HN where a bunch of people expressed their disappointment with the Chrome-ification of Google products. Seems sorta apropos to that thread.

Pretty nice - as a hardware synth guy, I have to say that the physical controls being offered here are quite inspiring. I only wish my Macbook had a touchscreen at this point ..
Also make sure to run experiment.consoleDance() in the console
I really like the transitions on this site. Material design is pretty awesome.
They're super choppy for me. What's your secret?
Maybe because (from about:gpu):

Accelerated 2d canvas is unstable in Linux at the moment Disabled Features: accelerated_2d_canvas

It works offline in Chrome - I think this might be Service Worker...
Yep, service worker is amazingly powerful!

FWIW, Chrome has a bug where SW doesn't intercept URLs changed using history.pushState(). If you're using the web app in Chrome 40, turning off wifi and navigating the site will show "blank pages". However, refreshing the page you land on does will work as expected while offline.

Good news is that it has been fixed in Chrome 41...coming soon! https://code.google.com/p/chromium/issues/detail?id=429972

Wow very beautiful job on the site. Very fun, yeah for Material Design :)
Are there usually any other tech events on during the week of IO? ie smaller conferences/meetups etc?
It's nice to see Google using Polymer.js on their pages.
Browser froze choppy horrible (Latest Chrome).

As computers get faster, our ability to program them in less efficient ways increases.

Even scrolling seems sort of "off" and choppy, at least on Safari (both OS X and iOS). It looks pretty I guess, but how the hell did they manage to mess up scrolling?
The page is completely blank with the latest Opera on Windows. It uses webkit so that's a little surprising.
Are you sure you don't have JS off or something? Looks fine to me in Opera.
I thought Opera was now built on Blink. Maybe I'm splitting hairs here, since Blink has webkit in it's ancestry, but being a fork, is starting to diverge.
Build amazing tools that we'll cancel in a year!

Becoming too cynical - help me.

You can't be blamed, they included an image of Google Glass right there on the page. Really, Google?
Google Glass is still internally under development. The public release candidate test has simply stopped. Maybe by May they have a new demo.
The site works! in IE9 mobile (WP internal browser), that's a pretty good job .) As choppy on my MBPR as any other full-screen image website.
In the past, Google I/O was home of big announcements of disruptive technologies.
This year it will be big announcements of Chrome-only technologies. </sarcasm>
The last couple Google I/O events have been disappointing because it takes an above-average amount of effort to get any of the neat things shown off (even six months or a year later). The most common example probably being that I don't know a single person running Android L. (Past examples might include Google Glass, and their Flagship phone, which someone I personally know was just recently able to order despite wanting to buy it since its announcement) Even taking into account that it was released after the announcement (November 2014, right?) It still seems awkwardly long. This isn't anecdotal either as can be seen in their dashboard: https://developer.android.com/about/dashboards/index.html
Google recently ships tech-demos, not products and I/O is one event where the hype starts.
It is hard even if you're a developer. I wanted to write Google Glass apps. No dice.
Yes, I was always looking for something like ART to be presented, given the sore state of Dalvik, and still cannot use it.

Also I don't have any hope for them to say anything about Java 8, treating NDK users (like myself) as first class citizens or any other alternative language. Specially given their attitude at Android Developers Fireside last year.

So iOS has Objective-C, C, C++, Swift, Objective-C++, JavaScript with access to the whole platform. IDE supports all languages.

WP gives me Javascript, C++, C++/CX, C#, VB.NET, F# with access to the whole platform. IDE supports all languages.

With Android, Java 6, partial Java 7, limited C and C++ with exposure to some Android and POSIX APIs. Studio only supports Java, even Eclipse NDK is kind of broken.

No support for Renderscript or GL shaders.

I'm wondering if it's worthwhile going to Google I/O. I haven't been to it before, but I'm thinking it might be useful for networking (in the social meaning of that word).

I'm just not sure if the $3000 or so (after paying for flights and hotel) is really worth it. Perhaps going to a local I/O event might be better?

The website is brilliantly created to embody Material Design.