One Step Forward, Two Steps Back

I’ve noticed this trend in WP development with new releases – apparently something is resolved when a new release is issued, but crap loads of things that worked before work no more. 2.8 was one of the worst releases ever and I could not believe I upgraded all my blogs from 2.7 as soon as 2.8 was released. It was the crappiest release in a long time. Many features that worked fine in 2.7 went to complete pooper in 2.8.

Subsequent sub releases were half decent and now bang – 2.8.4 beat 2.8 to the punch. By far the biggest step backwards in WP development since I started using WP. Why when you’re addressing a security issue you break 10 normally working features? I keep believing that each time I update my WP it’s gonna be better than the previous version, but it happens to be the other way around most of the time.

And the worst part is – when a working version is released, crappy update that breaks it is released soon thereafter so you don’t get to enjoy working version for too long. On the other hand, crappy version is never followed with a working one quickly. It always takes forever for an update to come after a piece of crap like 2.8.4 is released. What gives?