State of the Browser
It wouldn't be a stretch to say that spending 4 of my last 10 days at conferences has been overwhelming. Looking back, QCon was a great experience, but geared far more towards seasoned software engineers rather than anyone in the web development field. Apart from friday which had a great HTML5 track.
Today, I had the joy of attending the State of the Browser event in London.
With representatives from Google Chrome, Mozilla, Opera and towards the end, RIM, there was a lot to talk about and a lot to learn. There was a last minute change to the schedule with the Microsoft rep having to pull out due to personal matters, but he wasn't missed by me or many others. It was a great day for everyone to show where things had moved in the last 10 years or so.
As was rightly stated, 10 years ago, the situation was very different with browsers doing their best to sell themselves on their unique features. Although this may still happen in todays world, the collaboration and thought that goes into each new feature is impressive.
My browser of choice is currently Chrome and having seen Michael Mahemoff now speak twice, I've a great appreciation for where Google, Apple and the W3C have taken us. Mozilla really impressed today and Opera were a big surprise. All positive and all clearly proposing something different.
A member of the Mozilla team described Chrome as the window to the web, very little clutter, with the browser just delivering whatever is asked of it. Firefox was then described as a 'butler' in the sense that it not only delivers the web, when you ask for something a little more, Firefox is there to offer it to you. A fantastic analogy as for me, Chrome is what I expect of a browser, while my colleagues, friends and clients could all require something very different and find the Firefox, Opera or even IE offer that something.
The day offered two breakout sessions where I attended one talk on CSS3 by Chris Mills and another on optimizing web apps by Martle Ubl. The first was very interesting for me because I realised a few things I've struggled with CSS3 all comes down to documentation and a lack of time to experiment on my part. All things I'm going to push for both at home and work.
The HTML5 talk was a lot quicker but concise. Some of the advice was common sense on reflection but not always put into practice.
Why, in a loop, read and write again and again? Why not read and read and read and then write just once? Surely a lot quicker? It was described as being a magnitude faster, but I'm not sure how true that is. Would be interesting to see though. Especially versus a loop that contained multiple append()'s as apposed to .text() or .html() (jQuery methods).
Being on a Saturday was never going to be ideal, now I only have half a weekend, but I enjoyed it and took enough away for it to have been worthwhile. Big thumbs up!
Check out my State of the Web set on flickr and follow the feed on twitter.
This article was posted on by Charanjit Chana | 0 Comment(s) | lwsbrowser, state of the web, conference, browsers, web standards
| permalink
BeUnequaled Magazine