© 2003-2006 David Moles
Chrononautic Log |
|
Main |
|
I ☠ computers #210 o'clock, September 22, 2005(This is mostly in answer to Ben.) I never used any software in the 90s that was as painful to install, configure, use, or (god help us) upgrade as Apache or Postfix. I’m sure it was out there, but I wasn’t using it. (Admittedly, there are people who like mucking around in configuration files. I understand how such people could consider administering Apache to be less painful than administering, say, AppleShare. However, I am no longer one of these people.) I can’t speak to Google Earth because it only runs on Windows. But I’m not claiming that nobody today is writing good desktop software, or that the state of the art in desktop software hasn’t moved forward. I’m bitching about the state of the art in server and client/server software. SQL and I had our honeymoon. We still see each other from time to time, but the romance has long since gone out of the relationship. What’s not to like about MT being on mysql is that I don’t want to have to learn to be a mysql administrator just so I can have a blog. Admittedly, I’ve managed to get away without having to learn to be a mysql administrator so far, but the price of that is never being able to upgrade it or back it up. (For the record, all commercial RDBMSs that I’ve ever worked with suck from this point of view, too.) Likewise, the fact that you can hack the scripts MT is made of is certainly handy, but since I didn’t go to the trouble of, say, setting up a source control system and a test environment before I started hacking it, I now can’t remember what I’ve changed and when it comes to upgrading I have, again, screwed myself. As far as local vs. remote goes — well, I’ve been lucky, I guess. In twenty years I’ve never actually destroyed my own computer, or even come particularly close. And since we’re still five or ten years away (as the Glasgow Internet Experience showed) from me being able to access my stuff anywhere in the world from anywhere in the world, I prefer to keep the files I might want to look at where I can get at them. (Email is another story. But the primary use case for email is when I definitely am connected, not when I mgiht-or-might-not be.) Also, when it comes to remote file management, there’s this:
|
Comments |
|
I knew it! I knew you computer types looked at things like this! It's like WarGames. Next you'll be releasing chimpanzees, Brockerick. |
|
Hmm. I was furiously trying to correct the spelling of Broderick's last name and I made it worse. Oh well, next you'll be the star of a hit musical. |
|
I see. We're talking about two different things. You're talking about being an *adminstrator* of software. I'm talking about being a *user* of software... who occasionally likes to hack on it. I wouldn't set up my own Linux box in my house and install Apache on it and then MYSQL and then MT on top of that... god no. Particularly since I could STILL spill coffee on it. My web hosting company -- for the, what, ten bucks a month I pay them? -- installed Apache and MySQL, and patches them, and worries about upgrades and hackers and permissions and whatnot. I only installed MT, and it was pretty damn easy. And kept the original tar file around -- so if I really wanted to see what I've changed it's only an gunzip | tar -xf and a find . -exec diff away. I don't have to mess with the administration -- but I can still go actually poke at the database if I feel like it. This seems to me to be the optimal happy medium. I actually use a private MT blog as my general repository of private notes-to-self; at work I use a wiki for the same thing. Sure, this all assumes you're near an internet connection. But the thing is this -- I don't actually like computers all that much. For writing, for instance, I prefer pen and paper. For my hours off I like to have the computer put away and sealed up and be on the living room floor building block towers with my kids. For a palm pilot, I have business cards and a binder clip. If I actually want to use a computer, I might was well be on the internet and using server side software. For trips to Glasgow, the obvious solution is to room with Cory. See? Outsource the administration. (Those last three words would actually be a good rallying cry in many contexts...) —— Benjamin Rosenbaum, 3:25 PM, Thursday, September 22, 2005 |
|
Also, I grant you about the editing a rich text document in an HTML edit field. Not so great. That seems like a minor problem in comparison, to me, though. Hmmm, you could write your entries in eclipse and use a SQL ant task to post them to MT... someone should write an eclipse plugin... :-) 'kay I'll stop now. —— Benjamin Rosenbaum, 3:28 PM, Thursday, September 22, 2005 |
|
I've looked into paying someone else to administer things for me, but so far every place I've looked at, either it's not flexible enough, or the interfaces they provide for managing my stuff are even worse than administering my own system, or both. Possibly this just means I haven't looked hard enough. But maybe my real problem is with the concept of "administration". Nobody has to "administer" anything for me to use Photoshop. |
|
Actually, David, me and a whole bunch of other guys are working 24/7 to keep Photoshop up and running on your machine. |
|
Cool! Could they take over my mail server and web server and stuff too? |
|
Oops, I shoulda read this before posting a comment on that previous entry. For text areas (esp. in blogs), there are three general approaches I've heard recommended: 1. Desktop tools for posting to blogs. I've heard good things about Ecto, "a feature-rich desktop blogging client for MacOSX and Windows." I haven't yet used it, but I intend to. 2. If you use Firefox, there are extensions that make text-area editing a better experience. For example, a bunch of people swear by mozex, which unfortunately doesn't work on the Mac :( but which lets you use an external text editor to edit text areas. I also just came across Save Text Area, which lets you treat a text area like a text file you're editing. I would dearly love to use those tools, except that I don't like Firefox's GUI (much prefer Safari), and of course I'm on a Mac anyway so can't use Mozex (and don't have the expertise to help port it). 3. I have a vague notion that MT3.2 includes some GUI editing buttons, but (a) that doesn't really address your issue, and (b) those may not work (or even appear) in Safari at the moment; I'm a little unclear on that. Regarding upgrading MT: have you done enough hacking on the scripts that a diff wouldn't help? If not, I bet it would be possible to find an unaltered version of the original scripts for you to diff against. Alternatively, if you haven't messed with the database format, you could archive the altered scripts and do a clean install of a more recent MT version -- you would lose the changes you've made, but (depending on whether the newer version does things you want it to do) it might be worth it. If you have messed with the database format, you would probably need to do an export/import of the data somewhere along the way. ...Tell you what: if you want to try out MT3.2 to see what it's like, I'd be happy to set you up a test/sandbox blog on kith. (If you already know what 3.2 is like and that's not relevant, then never mind.) Anyway, I agree that you shouldn't have to be a MySQL administrator just to have a blog. But I don't think you need to be -- MT should handle any necessary upgrades to the database, and backing up a database is pretty easy if you've got the right tools. |
One countervailing concern, though, is hard drive death. Since i've just suffered through the first actual drive failure in my decade+ of being a computer user, i'm sensitive at the morning; when the drive stops spinning, all data is lost.
But that just calls for backups. :)