Guest post: May Roundup at SYWP

Wordpress LogoAs any of you who follow me on twitter will know, I have become a proud member of the South Yorkshire WordPress community.

One Tuesday night a month, my twitter feed becomes an irritating and alienating place for my followers, with endless repetitions of #sywp, alongside jabbering about SSL, Custom Post Types and the many amorous moods of @mkjones.

Since we are trying to publicise the community, we are hoping to make the official SYWP blog a little more lived in. As a result, I just wrote a roundup of this month’s meeting. There’s a snippet below:

This month was attended by the usual bunch of marauding geeks, with free coffee prepared and waitered by the servant hearted Kimb Jones. This nearly made up for the disappointment of Jag Gill failing to provide cake…

Anyway, there were three main talks this month (aside from the usual debates on the command line vs GUI, and on whether iPads are pointless). As ever, you can read back through the twitter stream for #sywp, and imagine you were there too.

First up was Paul Marshall, talking about his company’s experiences using Buddypress…

Read the rest at

Join us at the next SYWP at the GIST Hub on the 2nd Tuesday of every month. More information on the community group site

Firefox 4; an aborted review

The following brief post is about web browsers. If that’s not your thing, maybe go look at this beautiful photograph instead of reading on.

Just geeks left? Cool. I reluctantly jumped the Firefox train a year or so back, because Google Chrome has a faster javascript engine. That’s all really, but it is a lot faster at almost everything, and that makes a difference if you use the internet for stuff other than waiting for pages to load.

Time moves on, and Mozilla react to this by getting “super-duper fast” (their words not mine). So I decided to give it another go and get downloading. I installed beta 6, quite excited about getting back to grips with my previous favourite browser. And then I stopped. Didn’t even get as far as whipping out some JS heavy sites or anything. I had to stop, because the text anti-aliasing in the address bar is just… bad. 1999 bad. So bad that it hurts to look at tab titles. Or website addresses. #Fail bad.

Look at the horrific anti-aliasing!

Is anyone else getting this? Because I’m not even going to try the browser until they sort this out: Google 2, Mozilla 0 – sorry guys!

Note: A helpful commentor has pointed out that this aliasing bug is actually down to a glitch in the 2D hardware acceleration built into DirectX 10. So that means we need to revise the score. It’s now at Google 1, Mozilla 0, Microsoft -1. Much better!