Browser vendors take note: you can still be the first modern browser to implement a proper offline mode!
This was a common thread at several conferences, and the recent popularity of Parallels for browser testing barely scratches the surface. It's all very well saying that you'll always be using code built with your core language modifications in mind, but you may well change your tune when you try to incorporate Yahoo!
All of the example code for the HOWTOs was first written in an interactive prompt and then copied to a file once it was working.
I'm still using it, although some of the things I liked initially have faded while others have emerged.
I imagine the main problem was the heat - sitting in a stuffy lecture theatre on a night like Tuesday's wasn't a hugely attractive proposition, but the talks were more than worth it. They cover the bases effectively and each one offers something interesting that makes it worth studying in its own right. People often ask me the same back, so here are three things that have been catching my attention recently.
The big four all have active communities, which means less bugs, more support and a faster rate of improvement. or Google Maps and everything breaks. The talks really deserved to be seen by more people; if you weren't there you missed out on a treat.
I gave talks about it at both BarCamp and Euro Foo - it's decentralised single sign-on that works, and it's trivial to implement thanks to really solid libraries for most programming languages.
Overall though it rates extremely well. It went OK, but I really should have spent more time getting the slides right.
Another thing to keep an eye on. Don't use libraries as crutches; if you're not prepared to figure out what the library is doing for you you'll end up in a world of pain further down the line.
According to the authors, doing this with _javascript_ requires painful code forking.
Definitely the best value conference with the most grassroots atmosphere that I've ever been to. I can't wait for next year.
All were excellent, and each one nicely complemented the others.
getSelection and associated methods. Good _javascript_ code takes advantage of its dynamic, functional nature. If you plan to evaluate some existing libraries these make an excellent starting point.
They are a smart part of any.
Another thing to keep an eye on. All were excellent, and each one nicely complemented the others. Programmers on those VMs get more productive languages, while users of those languages gain access to enormous existing class libraries, not to mention the promise of significant performance boosts.