zzzzzzzzzzz

2.1 is out. Yawn. Nothing here we haven’t had on .com for months already, and you didn’t see me shifting my self-hosted stuff over here to partake of the fantastic new features. You can see why Matt kept forgetting what was in it.

If 2.2 is timetabled for April they’re really going to be struggling for new stuff to trumpet. I predict built-in Snap previews, Sonific in core and another page from Shuttle.

7 Comments »

  1. Collin said

    It’s funny you know, I had almost the same reaction. The only thing I did notice was that UTW breaks in 2.1, as reported by other people). I haven’t bothered upgrading.

  2. I predict: Atom 1.0, Atom Publishing Protocol, better draft management and workflow, malformed plugin protection (have WP test it before activating it so it doesn’t break your admin), speed optimizations and improvement of page scaling (somewhere around 1000 pages things start to fall apart), integrated notification of plugin updates (and maybe WP updates too), integrated tagging (without losing categorization).

    I also predict that I’m not going to get much sleep in the next two months.🙂

  3. Atom 1.0 should have been in this release, and would have been if its omission hadn’t become a point of principle for Matt. Speed and scaling improvements only affect a tiny minority of users. Better plugin handling sounds good, but honestly? I’ve yet to hear anything that would make it worth switching from 2.0, especially since you’re committed to maintaining it for the foreseeable future and won’t be able to play the ‘more secure’ card. Mostly, I don’t want my post and link categories merged, though I could probably reconcile myself to it if page categorisation was added.😉

  4. Root said

    Atom? Its in Habari right now:)

  5. Matt performed his Atom 1.0 mea culpa and penance last night. The problem, in my opinion, was that 2.1’s release date kept slipping. Last Spring or Summer, there were some good arguments for not moving to Atom 1.0 quite yet. Not so much now. The “no Atom 1.0 for WP 2.1” stake was put in the ground early, and wasn’t moved when the release date slipped. Hopefully shorter development cycles will help this.

    I’m hoping that with 2.2 forward, my commitment to 2.0.x maintenance will serve as motivation for kickass features in trunk. Without the security motivation there, it’s going to be up to core features and enhanced plugin abilities to prompt the upgrade urge.

    And shh, but I really don’t like the category merging either. Well, let me clarify: I have a viscerally negative reaction. On paper, it looks great, and it gives you hierarchy and nesting and quick-adding which is nice… and it consolidated a lot of code on the backend. I just object to it for the same reason I object to casseroles. Sometimes I want to eat turkey and not have to think about mashed potatoes and peas.

  6. Root said

    Casseroles? I can’t stand them.

  7. […] I haven’t been this bored since 2.1 was released. […]

RSS feed for comments on this post · TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s