Dunno, maybe offtopic, but who else, except folks on this list, can answer? I write tons of perl. Mostly weblications (wouldn't know an MPW if it bit me in the toolbox). Mostly lands on sparcs. Mostly for for inter/intranet users. All of it written on one of my macs. The allure of contracting a little perl sang its siren song and I discover that zdnet is right. There's plenty-o-windows out there. And IS people are cranky about macs. Emotional, irrational, zealous, hatred for macs exists. I develop perl that lands on solaris. Them little bytes seem to work just fine. ('cept for some pesky endian things between mac and solaris or is it linux, I can never remember.) The combination of BBEdit and MacPerl (plus the subtleties of MacOS) don't exist on the wintel platform. (I looked, I've got a 95, a 98, and a 3.1 machine snaked through an omniview with my mac. I ended up with homesite, pfe and activestate all thwarting me in production workflow. And I practiced this "MSdos/Command Prompt This Dammit" for months.) For web production MacPerl/BBEdit is especially cool, because I can code, test, check and deploy sometimes without ever touching the mouse. (gotta admit the compaq mouse through the omniview, driving the mac, alarms mac-savvy guests.) Bottom line is that my mac gives me a workflow that is unparalleled/unachievable on the wintelly side. My question is: Is there any empirical data on Mac/Perl/Web workflow, or must I rely on anecdotal murmurings? BTW, I welcome anecdotal murmurings if that's all we got, but boyoboy would I love numbers. You know, 100 monkeys, with macs would have hit the Illiad 6.3 times faster than using wintel. Or something. PS. Did I miss something? Look where Mathew is working. Cool. Congrats. # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org