Leopard’s ultra-easy screen sharing has made it a breeze to help my mom with her new Mac. Today I used it for some more fun. I created my first working Yahoo! pipe, a merging of my MJ photos and Gloria’s. Then I connected to my mom’s computer with Leopard’s excellent VNC client and subscribed her Mail.app to my new pipe feed. I ran TextEdit and put a note on her desktop about what I’d done.
For a long time, my parents have been held hostage by AOL. AOL, for ages, made it nearly impossible to use any tool other than their mega-integrated awful front end to The Internet. Even once they set up IMAP, you were stuck with their Favorites and Address Book. This was a big deal for my dad, who has a gigantic contact list. I’ve been heckling him to use Apple’s Address Book for ages, but he couldn’t get out.
I’ve been using OmniFocus since pretty early on in the private beta. It started out pretty good and has gotten very, very good. For years, I have said that nothing is as effective as index cards. OmniFocus replaced my index cards a few months ago.
Email is tough. It’s very, very complicated, which is a big problem, because from the outside it seems so simple: it’s like some headers and then a body or two, right? I try to advise people that Mail::Message is not as crazy as everyone implies, but people really like to use something really, really simple, and it leads to problems – one of which is trying to figure out where the ideal distinction between “just enough” and “too much” is.
I’ve been running Leopard for just over a week, and it’s a really mixed bag. My memory is that Tiger and Panther were only annoying because they failed to fix things I wanted fixed. Leopard has broken quite a bunch of stuff, and I afraid that some of it just isn’t going to get fixed.
For quite a while now, I’ve used SuperDuper! to do backups. It’s basically a nice GUI over a rsync. The common use it to tell it “make drive B into an exact duplicate of drive A.” It does so as quickly as possible, changing only the files that need to be changed. This means that after your initial backup, you can make a new backup very quickly by updating the initial backup.
Since the very, very early days of Sub::Exporter, it was clear that it would be
really useful to be able to replace the way that exporting itself occurs. That
is: the way that routines are generated and installed, based on configuration,
gathered collections, and other user arguments to the generated
I first started using procmail around 1993, I guess, when I got my first access to the Internet through my dad’s alumni account at Lehigh University. The only programming language I knew was C (and things that don’t count, like Logo and BASIC), so procmail was like magic.
Earlier this week, I read the final of the Fletch books. (Actually, I read the final Son of Fletch book. The distinction isn’t that important.) I’m looking forward to reading the Flynn series, which is something of a spin-off.
I liked Damian Conway’s book Perl Best Practices. It had a lot of sound advice that can help a programmer or programming group decide on a set of house rules. For those who aren’t interested in making a lot of decisions, it can even be used as a pre-built set of standards (although a few of its suggestions, generally those involving modules releaed by Damian for the book, are untenable).