One of the hardest things about Microformats is explaining their benefits to people. You can say “It’s a standardised format of marking-up content, which is both human and machine readable!” until you’re blue in the face, but until you can show people a practical benefit they usually remain unmoved.
Luckily there are a few tools out there which will help you show off the benefits of using Microformats, and involve little work from you.
While Firefox 3 is a really fast & usable browser, I was a little disappointed by the (comparative) lack of really new features in the rendering engine; that’s not to say there aren’t any, as there are plenty, but that Safari 3.1 and Opera 9.5 have set the bar very high in their latest iterations.
So that’s why I was delighted to hear about the 3.1 release of my favourite browser, and doubly delighted when I found out which features the team are planning to work on for inclusion in it:
As is customary (or as customary as ‘twice’ can be), here is a quick round-up of the sessions I attended at @media this year, with links to slides where available (which, as I type this, is pretty much unavailable).
Sessions which I found particularly interesting should be covered in more detail later, and I’ll update here as I find more presentations.
Having missed the opening party, my introduction to London Web Week was last night’s Microformats vEvent. Unfortunately it wasn’t a good introduction, for two reasons;
First (and foremost), it wasn’t really about Microformats. The first speaker talked about RDFa and GRDDL, the second about RDFa and FOAF.
Second, the presumption was that we had an extremely high level of technical knowledge; a presumption that wasn’t true, in my case at least. I’m fairly new to Microformats but I have a pretty good idea of what they’re about; both talks went over my head anyway. And my poor wife, who’s learning about them for the first time, had no idea what was going on.
The description of the event said:
We hope that no matter your experience level, you’ll find the evening informative, enjoyable and inspiring.
I didn’t. In fact, it may well have been counter-productive for me; it took a subject I’m excited about, and made it sound complicated and boring.
I’m sure that some people would have got a lot out of it – the man next to me who’s studying for his pHD in artificial intelligence certainly seemed to enjoy it – but I think the organisers should have been more honest about the technical knowledge required, and saved some attendees a bit of time.
I did get a book for asking a question, however, so it wasn’t a total loss.
The W3C came under a lot of heavy flak last year for being slow, cumbersome, bureaucratic, etc; there were calls for a CSS2.2 (which I seconded) which rounded up all the existing implemented features, and for the CSS Working Group to be disbanded – a lighter, alternative task force, the CSS Eleven, was set up to try and make sense of it all. But as we’ve heard nothing from them in the six months since they were set up, I think the Eleven have found it’s not as easy as it looks.
The CSS WG has a new chair now, including the passionate Daniel Glazman, and it seems to be refocused and refreshed, which is good news; in his latest blog post, he says that the WG is aiming for RECs, RECs, RECs
. If that’s the case, maybe we can start to get excited.
It’s an exciting time to be a web developer, as all four major browsers have released / are releasing new versions with extended CSS & HTML support. However, as Opera and Webkit race to be the first to score 100% on the Acid3 test, a lot of people are getting caught up in the excitement and turning this into some kind of pissing contest.
Honestly, it doesn’t matter who passes the test first. Does it matter who passed the Acid2 test first? Do you remember? Do you care? What matters is that this year we’re going to have much better standards support and less proprietary bugs, and that’s the best and most important thing.
As with operating systems and video games consoles, everyone feels the need to take a side and defend it vigorously. But it’s not important. If you like Safari, then all power to you; I prefer Firefox. What we can agree on is that we want our websites to work equally well on both of them. I congratulate Opera and Webkit equally for working towards making better browsers, and couldn’t care less who passes the arbitrary test first.
That said, it should be judged by whichever one makes a production release, of course, not a nightly or an Alpha. You don’t win a race by having the fastest trainers, you win it by crossing the finishing line!
On a related note, today’s Wired has a good summary of HTML5 support in current and forthcoming browsers.