Switching Spring
Apparently, it’s spring, when a young blogger’s fancy turns to thoughts of switching:
ShelleyGeorge switched from MT to WordPress- Phil Ulrich switched from blosxom to WordPress
- Lisa-Jill switched from MT to Textpattern
- Jeremy’s switching to a sweet new Powerbook
And of course, lots more people switching things I’ve forgotten, or I’m too lazy to look for a link to. Besides, it’ll just make me feel worse about the rut I’m stuck in, and you can do that for me in the comments just as easily. Go on, you know you want to: what happy change have you made this spring?
You can now call me George.
I started working out and am now so frighteningly bulgy and buff that I am considering running for governor of California. I kill you last…
(PS : Hi George!)
Does it count if I also switched an XP machine to freebsd? ;) And switching schools! I’m on a roll here…. ;)
I’ve switched from solid foods and satisfying bowel movements to a 102 fever, ginger ale and diarrhea. My doctor assures me it’s only temporary though. On the plus side, I’ve lost 4 pounds in 48 hours. On the down side, that’s probably temporary too.
Bleah. Thanks, I feel better about my rut :)
Too much information. ;-)
Ah, shoot. I did my switch too early. I switched from MT to Blosxom during the winter.
I did mine too early, too. I switched from MT to Textpattern right around April 1, and people thought it was a joke. But I’m still pretty serious about it.
Converting my weblog to PDF’s, that was the joke.
Ooh, a PDF blog. Now there’s a devilish idea.
Nah, it’d be too much work. HTMLDoc doesn’t support CSS, and I’d have to recreate my current design in tables and font tags. Who needs this grief?
I considered switching to Textpattern, but it didn’t support ETags or Last-Modified headers.
I considered switching to WordPress, but it didn’t support ETags or Last-Modified headers.
I dislike the ”Rebuild” cycle as much as the next guy, but at least Apache gets HTTP right.
For the record, I have it directly from the WP developers that the upcoming version 1.2 supports both ETags and Last-Modified headers. And it already has comment moderation. Of course, the upcoming MT 3.0 has TypeKey. Oh, such choices. How shall I restrict the free speech of hysterical bloggers?
304 support is a deal-breaker though. I can’t even consider stifling free speech until I get ETags and Last-Modified headers.
Well, although it doesn’t help your end of the bargain (you still have to run your PHP and do all your db accesses), mnot’s cgi_buffer does a pretty nice job of giving you 304 support at the cost of one line of prepend and one line of append.
But, yes, I’d really rather have genuine file caching. As long as I don’t have to write it in a way that can easily be deployed on anybody’s shared host no matter what.
Yeah, cgi_buffer rocks, but I couldn’t get it to run under Python 2.3. Dunno why.
I may simply set up my own funky caching system. After all, I don’t want my feed URLs to change, because we *know* how bad clients are about following permanent redirects and updating their cached URL.
But I’ll probably just end up sticking with MT. Boy, it’d be nice to get my hands on that 3.0 beta. Who do I have to blow in this joint to get a damn beta?
I’ll email you the password.
…
Oops, unable to connect to b.com.