On Hacks, bugs, and tools
This is pretty neat. For whatever reason, Internet Explorer has a quirk about how it interprets CSS properties. So, the CSS maintainers adopt a clarification to their rules (in CSS 2.1) which explicitly allows the quirk, and it becomes a way for web authors to recognize and adapt to any other idiosyncrasies that happened to make their way into IE.
I’ve been thinking about idiosyncrasies and coding lately– mostly because I’ve been laying out a new poster for display at the 2009 ISIE conference in Lisbon, which I sadly won’t be able to attend, owing (at some distance) to California’s present financial difficulties. But at least my poster will kick ass. I laid it out in TeX using the “arbitrary” class, a derivative of a0poster which appears to be missing from the comprehensive TeX archive network. Anyway, it’s the only way I know of to make a 48″x36″ PDF in LaTeX.
Every time I sit down to use TeX I end up whiling away the hours.. Sunday night I picked up the poster I had made for SBC 2008, which I had been very happy with, to adapt it to the new conference. It took me probably 90 minutes to solve a technical issue on the install that I had already solved at least once before (it was my first time making a poster on a new laptop, and I probably solved it the same way on the last machine the last time I made a poster). Whenever I spend time solving the same problems multiple times it gives me an opportunity to berate myself for using such idiosyncratic software when anyone “sensible” (implicitly including everyone else in my department and, it seems, the entire conference-attending public) uses PowerPoint.
Instead I find myself investing 4 hours into learning how to plot data with PSTricks… maybe 6… anyway, it was spread out over two days and involved searching for bugs and bug fixes. Because doing new stuff in TeX never works properly the first several times through.
Searching for bugs and bug fixes is the characteristic behavior in the use of open-source technology. Because anyone can contribute solutions (some projects have broader user participation than others– compare TeX to, say, octave-forge), the question faced by the user is, “How have other people solved this problem?” And that was how I came to search for bugs in the pstricks “\savedata” mechanism and found this. Or something very similar. Behold! The problem had long ago (1997) been discovered and worked around. I just have to make sure that I don’t use \savedata inside another macro, otherwise it won’t work. Anyway, now I could continue with my work. Only took 45 minutes of troubleshooting followed by 5 minutes of google.
I don’t suppose anything like that ever comes up in PowerPoint when you’re using its built-in data-plotter and axes-maker, but I wouldn’t know.
So I berate myself. Maybe if I weren’t distracted by all the technical difficulties, I would get more real work done. I spend all this time solving all these problems and what do I have to show for it?
(Aside from carpal tunnel collapse and a sore neck, I mean): A beautiful poster. Entirely TeX (though it is a bit of a mess: source). It turns out that yes, it is the right tool for the job. If you have the time to sink into it.
I’m sure it’s possible to make the same poster in PowerPoint (plus, probably, Excel.. and EndNote.. ) but for now I’ll stick to the tools I [more or less] know. I wouldn’t go so far as to say TeX is pleasant to work with, but at least I can grope my way through it when there’s a problem. And maybe I do need an instruction manual every time I want to change arrow styles. But hey- that’s why I have multiple desktops.