Post Format

WordPress Reaches 2.7 And Open Source Software

My move from Movable Type to WordPress (the software that powers this site, barring the forum) just over a year ago has turned out to be a great choice with hindsight. At the time I liked the look and extensibility options of WordPress and the fact that a vibrant community had built up around it so I switched and I’ve never looked back.

Ever since then I’ve become a bit of a WordPress evangelist to friends and have used it to build a few sites and encouraged other people I know to do the same. I like to keep an eye on the next version as it’s being developed and have a local copy on my computer that I play with. Early through the 2.7 development process it became clear to me that 2.7 was going to be very good. Things like threaded comments, paged comments, sticky posts, auto-updates, bulk editing and above all the revamped administration interface so impressed me that I started using the bleeding edge builds on this site. I’ve been working in the software industry a long time and have learned to steer clear of beta builds of applications I depend upon (particularly Microsoft ones I have to say) – I’ve been burned too many times to count. But with WordPress I felt differently, and it’s all about the people who work on it and the way it’s developed.

The New-Look WordPress 2.7 Dashboard

Coming from a corporate development background as I do I’d always assumed that popular open source projects would mean a lot of people pulling in different directions and therefore require a lot of management overhead to filter out the noise and move the product onwards. I assumed that outside of the more rigid “need to make money out of this” corporate environment open source projects would tend to bumble along rather than stride along. But watching the WordPress development process has shown me that I was quite wrong and pretty much the opposite is true.

The more people who use a particular piece of software the more they’ll want it to do this little thing that nobody else would use but they absolutely want and will moan and complain if it doesn’t (I get plenty of that with John’s Background Switcher and that’s nowhere near as popular as something like WordPress). Or you get passionate people who love the product but want to pull it in different directions and won’t back down. A handful of these people can result in a lot of bickering and momentum slows. In the corporate world you’re either a slave to these people and have to create some Frankenstein’s monster of a product to please everybody (making compromises) along the way or they can be ignored completely which is easier as the development process isn’t publicly visible like an open source project is.

What I like about WordPress is that there are a bunch of talented people, passionate about what they do working on it. Matt steers the ship and can have the final say on something that needs the final say, anybody can contribute their suggestions, ideas, bug fixes and so forth and rather than having battles as to what direction WordPress goes in, there’s always the option of “if you don’t like it, fork it and go your own way”. This was how WordPress itself started, as a fork of b2. If someone comes up with a great idea that improves WordPress then there’s every chance it’ll make it into the product. Since the type of person who contributes to the development of WordPress will be passionate and care about the product, they want to make it better for everybody. And as the development process is open to all, there’s no excuse to not be connected to its evolution.

So where was I before I went off on a tangent? Oh yes, installing the bleeding edge version of WordPress 2.7 here. I could watch the development of 2.7 unfold in front of my eyes and if I found something wrong I could raise a bug report or even submit a fix (as could anybody else) and knowing the quality, dedication and passion of the people working on it and seeing how great it was going to be, I wanted to start using it as soon as I could. And you know what? WordPress 2.7 is even better than I thought it would be!

WordPress99% of the people who use WordPress no doubt have little interest in its development (quite rightly, being users rather than developers) and the first they know about a new version is either when it’s released or when they read posts prior to release discussing new functionality. Some may moan and complain about releases being too frequent or changes that they didn’t think were necessary (like another redesign less than a year after the last one), but when you see the amount of work, care and thought that goes into each release and the reasoning behind all the decisions (such as the latest redesign making it a platform to take WordPress far further than was possible before), it’s clear to me that they’re doing the right thing and WordPress is in good hands. And if you don’t like it, you can always fork it and take it in your own direction. But I wouldn’t recommend it as you’ll find out just how hard it is to create successful software that people will love. Software like WordPress.

Anyway, if you’ve never used WordPress, go and take a look and if you’re already a user, read all about the new version here. Quite simply, it rocks! Oh yes, and open source isn’t bad either! ;)

Posted by

Scotsman, footballer, software developer, bounty hunter, photographer, dog owner, risk taker, heart breaker, nice guy. Some of those are lies.

11 Comments

  1. One of the reasons I’m going to move away from WordPress is that I simply couldn’t get it to format the code correctly in one of my blog entries. Perhaps it would do in 2.7.

    Also, what does the Turbo link do?!

    • That’s a bit of a dog’s dinner you’ve got there! For one thing the CSS style for code wants to not justify the text. You’re also a bit hampered by the width of your pages. Personally I wouldn’t have used ‘code’ at all, I’d have either used some other style, maybe just ‘em’ of made the code into ‘pre’ blocks. I used that on this post in conjunction with a plugin that formats code rather nicely to good effect. I do sometimes switch to code view myself but it’s very rare and generally only if I want to add a particular style to a div or something similar. Maybe I’m just less demanding from a formatting point of view than you! Although WP 2.7 does use the latest and greatest version of TinyMCE…

      Oh, the Turbo link is so that Google Gears can cache all the static WordPress files which speeds it up somewhat!

  2. Ah yes, WordPress rocks alright. Just upgraded to v2.7 myself as well and it went smooth as a babies bottom. I’m glad to see the auto-upgrade feature in there personally. If it works as well as the plugin upgrade feature, it’ll be awesome!

    <code> or <pre> should do the trick for formatting your sourcecode snippets btw. When things go pearshaped in the WYSYWIG editor, I use the HTML editor to code some HTML tags the oldskool way.
    Quite geeky hardcore isn’t it?

    • I actually update my WordPress install through SVN but if you don’t have shell access to your host then the auto-update will make life a hell of a lot easier!

      Oh and I fixed up the HTML in your comment that went awry – how ironic after John complaining about formatting in WordPress! :)

  3. I used the <code> element because that’s the correct semantic element to use for marking up…code! The funny thing is that I never use the WYSIWYG editor, but it still mangled it.

  4. Looked at WP a while back, at the time there wasn’t a simple way of importing my Drupal site, not sure there is now, but I’ll take another look…. anything that ensures I can maintain my rubbish excuse for a website with a min of work has to be a good thing.

    • Heh heh, don’t sell yourself short Dave! I’ve seen a couple of places that talk about importing a Drupal 5.x site to WordPress so it’s possible (although I think you have to import to an older version of WP and upgrade). Although I do hear good things about Drupal too!

      Oh, nice Gravatar btw, very seasonal! :)

  5. Got WP running locally now, plus a copy of my Drupal DB, maybe time for a play, always good to have something to do over Christmas that isn’t work or family related (well I think so)

    Gravatar was from a fun run I did a couple of weeks back

  6. “if” I’m banking on “when” – festive cheer or family arguments…
    ;-)

Comments are closed.