WordPress, the publishing engine that powers this site, has today seen the release of of an update to version 2.04. It can be warmly welcomed as it not only fixes more old bugs but corrects the mistakes that were left loose in 2.03 and secures some further vulnerabilities that have come to light. I for one, am quite happy with the progress of WordPress. Since I first started to learn my way round it just prior to the release of 1.5, it has become more rugged and, I believe, faster and more responsive.
Also in the works is the next future major release – 2.1 – which I have been playing with for the last few days, the second alpha being available for anyone who wants to see what is coming along soon. As anyone would expect, there are things I like and things I don’t which was also the case with 2.0 and most probably applies to most users. Surely everyone has a ‘feature’ they desperately want to see included just as there are new things implemented that make you scratch your head and wonder who on earth thought it would be a good idea.
What I don’t see and what is very much needed, is a re-visit to some of the older code to bring about some consistency of approach and to clean up some glaring disparities. I for one, and I suspect I am not alone, would prefer to see some effort going in to improving what is already there and making it more usable and consistent than simply adding new features for the sake of it – especially when they are of questionable importance and even more so when they have a negative effect on currently developed themes and plugins.