A lot of web developers, at least over the years, seem to have fallen for Microformats. Naturally, the given question then is: do we really need Microformats?
I have been interviewed for DZone/Web Builder Zone, where I mainly talk about DOMAssistant. Hopefully you get answers to some questions you have possibly had. 
Today I thought we’d talk about how, or rather were in the document, to include JavaScript files.
Having had a number of jobs and from being a consultant, getting the opportunity to see how a lot of companies and clients work over the years, I’m way too often surprised how underestimated cooperation and keeping a competence available throughout a project really is.
Writing about whether people validate their CSS, it made me wonder about how/if people ensure the quality of their JavaScript code.
We all heavily evangelize the validating of HTML code and think it’s just a given, right? But how about the CSS code?
For some time, I’ve wanted to play around with Adobe AIR and see what it’s like. I’m also a sucker for very simple, yet addictive, games, so now was the time!
When developing JavaScript, performance is one of the vital things. Therefore, I thought I’d share the performance of loops with JavaScript, and give some advice.
The new version of DOMAssistant, 2.7, is finally out and my impression is that it is a very stable and solid release. Faster CSS selector performance, new features while at the same time a smaller file size.
Now there’s a plugin available to get the best features of ASP.NET into Ruby on Rails.
A casual gray Friday like this, I was thinking about the best terms about web developers I’ve heard.
It’s about time for another Geek meet, don’t you think?
When I read the news this morning, it blew my mind! Microsoft will use the Gecko layout engine for IE 8.
