Paradoxically, the more time saving abstractions you are using the more you actually have to know.
The big four all have active communities, which means less bugs, more support and a faster rate of improvement. With any luck it will become part of the accepted accessibility benchmark - I know I'll be testing sites with it in the future.
Ajax requests are instead made through an invisible Flash file that uses Flash to load the data, parse the XML, extract some CDATA and pass it back to _javascript_ to replace a div. Safari and Firefox both have extensions that enable this but it's great to see it built in to the core product. , Technorati and Google search results pages which don't have those links.
In _javascript_, that means that libraries that mess with Object. Here's hoping other browser manufacturers follow suit.
It went OK, but I really should have spent more time getting the slides right. They're APIs that you call over the Web. They're APIs that you call over the Web.
If you rely on a library to abstract away the browser bugs from you you are certain to run in to a bug that you can't fix sooner or later.
Another thing to keep an eye on.
Even Gmail works, thanks to an automatic fallback to their plain-old-HTML interface. or Google Maps and everything breaks. Even Gmail works, thanks to an automatic fallback to their plain-old-HTML interface. Clever, but a bit scary at the same time.
Definitely the best value conference with the most grassroots atmosphere that I've ever been to. If you plan to evaluate some existing libraries these make an excellent starting point. With any luck it will become part of the accepted accessibility benchmark - I know I'll be testing sites with it in the future.
I suppose it's looking for any link on the page with 'Next' as the link text.
OCaml is a pure functional programming language with type inference, an object system and a strong collection of libraries.
They cover the bases effectively and each one offers something interesting that makes it worth studying in its own right.
In _javascript_, that means that libraries that mess with Object. Test-first development is certainly an important technique, but the power of interactive development should never be underestimated. I can't wait for next year.
The slides were on automatic, so the presenters had to be able to time their talk precisely to match up with their slides. The big four all have active communities, which means less bugs, more support and a faster rate of improvement. 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!
A visual indicator that you are viewing an offline document would be a very useful addition. I'll report back on the experience later. Whatever it's doing, it works surprisingly well. If you rely on a library to abstract away the browser bugs from you you are certain to run in to a bug that you can't fix sooner or later. They're APIs that you call over the Web.
Here's hoping other browser manufacturers follow suit.
The big four all have active communities, which means less bugs, more support and a faster rate of improvement.
With any luck it will become part of the accepted accessibility benchmark - I know I'll be testing sites with it in the future. YDN is one of my favourite parts of Yahoo!
Both were excellent events in their own right, and great examples of event organisation done on a small to non-existent budget. OCaml is a pure functional programming language with type inference, an object system and a strong collection of libraries.