Stop using Ajax ... and start using Opera Kestrel beta 2!
Friday, 25. April 2008, 11:10:28
Hi folks, hope you are all well, and not too bored that this next blog post has taken so long. The title is a bit contrived, and is actually an amalgamation of the two things I was going to tell you about. Things have been pretty busy at Opera lately!
First of all, we've got another exciting new beta release of Kestrel, the new Opera desktop browser - beta 2, to be exact. It's got some exciting new additions, such as support for full CSS3 selectors and hsl, support for MathML, further speed optimizations, support for HTML5's getElementsByClassName, and improved synchronization of bookmarks speed dial sites and other settings through Opera Link. Download it and play around.
Next, I've published a very interesting article on dev.opera.com written by the delectable Brothercake, called Stop using Ajax! This article comments on how Ajax can do amazing things, but is often used gratuitously and unnecessarily, at the expense of accessibility. Cake makes a great argument here, and I think this should act as a wake up call to any developer to just think about what they are doing a bit more carefully, and take care that their application functionality doesn't end up locking out significant parts of their target audience.
First of all, we've got another exciting new beta release of Kestrel, the new Opera desktop browser - beta 2, to be exact. It's got some exciting new additions, such as support for full CSS3 selectors and hsl, support for MathML, further speed optimizations, support for HTML5's getElementsByClassName, and improved synchronization of bookmarks speed dial sites and other settings through Opera Link. Download it and play around.
Next, I've published a very interesting article on dev.opera.com written by the delectable Brothercake, called Stop using Ajax! This article comments on how Ajax can do amazing things, but is often used gratuitously and unnecessarily, at the expense of accessibility. Cake makes a great argument here, and I think this should act as a wake up call to any developer to just think about what they are doing a bit more carefully, and take care that their application functionality doesn't end up locking out significant parts of their target audience.
