I’m now running Wordpress 2.2. I haven’t really noticed any changes personally but then again the details on the upgrade suggest that the major changes are to widgets (which I don’t use yet) and hooks for developers (which I don’t do either).
I’m glad to hear that they’re trying to make things better for developers though. The entire reason I chose to go with Wordpress in the first place was that I didn’t want to put any effort at all into the content management of this blog. That of course is a ridiculous goal to have, so I’ve settled for minimal effort. That means I don’t want to develop. I want other people to do it. Therefore the easier and more powerful the hooks into Wordpress are, I benefit indirectly since the developers out there will be able to do more in less time. Everybody’s happy 
(No Ratings Yet)
Loading ...
4 responses so far ↓
1 Ian // May 16, 2007 at 8:19 pm
Speed optimizations, feh.
They pushed the tagging implementation off to 2.3, so it looks like I’ll be following SVN for another couple months. Mercifully for me it seems pretty stable. Hopefully something comes of their summer of code projects, some of the suggested ideas there include overhauls of the caching system (including fragment caching) and selective loading, which could really improve the load times of Wordpress pages.
That would be great if it came through.
2 Marc // May 16, 2007 at 8:55 pm
I was wondering about the tagging. It’s not that big a deal for me to wait since I’m patient on this issue
Have fun with the SVN 
I haven’t really been paying much attention to the summer of code thing, but have noticed it on the dashboard a few times. Anything that will speed Wordpress up would be wonderful. The speed improvements they’ve made since 1.5 have been great, but it couldn’t hurt to go faster
3 Ian // May 17, 2007 at 6:43 pm
I’m unconvinced they’ve actually made any significant improvements. If anything 2.x seems slower, although I haven’t done any benchmarking. I do know that there’s a javascript somewhere in the dashboard that causes me problems with Konqueror or Firefox on Linux (100% cpu for long enough for the OS to realize “hey, this isn’t responding”) … but I doubt that’s high priority for anyone to fix.
Fragment caching and selective loading would be great though. I’m not sure if they can be done in a way that doesn’t completely break dynamic plugins without significant architectural changes though… essentially the same problem Typo had (it used to generate static html pages), except Typo got to fall back on the built-in rails fragment caching. Wordpress obviously can’t do that.
Interesting to see what happens.
4 Marc // May 18, 2007 at 10:12 pm
In my anecdotal experience, it’s been a bit faster. I haven’t benchmarked anything and I know the SQL query time varies wildly through the day anyways so it’s tough to benchmark in terms of real world performance. I hate those javascript problems. I’ve had some in the past.
As for the rest, I’m eager to see the continued developments too. Not to the technical level you are, but still interested nonetheless
Anything that will help Wordpress scale better can’t hurt at all.