Facebook.com/TedCarnahan
LinkedIn.com/in/TedCarnahan
Twitter.com/TedCarnahan
“Freedom Software” versus “Free Software”
“‘Tis but thy name that is my enemy; …O, be some other name! What’s in a name? That which we call a rose by any other name would smell as sweet…” – Shakespeare, Romeo and Juliet
Perhaps the most frustrating thing for me as an advocate for the use of Free(dom) software in the church is explaining the term “Free Software.” What does that mean? Most people, hearing that name, think “freeware” – any software that is free to use without serious limitations. But, of course, that’s only half of the meaning behind the term.
Why Open Source Software is like Church Coffee Beans
No organization in the United States has a stronger incentive for using open source software than the Church.
“The Church is always asking for money!” – Everyone.
In a way, that’s right; the church is always in need of money. Money for ministry, outreach, and evangelism. Money for books and materials. Money to pay salaries and maintain facilities. Money to pay for seminary education (I had to slide that one in!). And so on. Sure, there are preachers who extort money from their parishioners, flying around in private jets and all that, but every church I’ve ever been in has a budget to meet. Those budgets are met with contributions offered to God, and church staffs have a responsibility to manage that money wisely.
Church budgets are zero-sum. Money spent on administrative overhead (e.g. computers and software) can’t be spent on education, mission, and ministry. The most compelling argument for open source software in churches, therefore, is that open source is Free.
But, churches are non-profit institutions. Instead of paying hundreds of dollars for Microsoft Office, you might get a Microsoft Charity License for $50. Many vendors are now providing this service for non-profit organizations. This drives the cost of software acquisition down, and proprietary software begins to look attractive again. Oh, how the waters are muddied!
I’m not going to lie: it’s hard to argue against cheap MS Office. But when you examine the total cost of ownership of both proprietary and open source software, you also have to consider the hidden costs. Maintaining up-to-date records of all of your software licenses, ensuring that your church’s license keys aren’t borrowed and used for other purposes, etc. can drive up the cost of proprietary software dramatically. Nevertheless, it may still seem less expensive to choose proprietary software.
So if church budgets are tightly constrained, and managing money wisely is a matter of responsibility to God, then why pay more for software? The same reason people buy Fair Trade Coffee. Not only does it taste better, but by buying fair trade coffee you support sustainable agriculture and economic justice.
Churches (in particular) have already embraced the responsibility of paying slightly more for a better quality product that is better aligned with their goal of justice for the world. Open source software is better quality and more consonant with Christian principles than proprietary software. If the principles of open source are more fair and just, the church ought to give it priority over proprietary software, even if it costs us slightly more to implement.
I plan to write further on the relationship between Christian doctrine and open source software. In the meantime, thank you to the many readers and commenters of my first article in this series.
Three steps to Open Source in the Church
The history and legacy of the Church in the late 1990s and 2000s will be lost in 10 years because we will lack the software to open its’ data.
Check out this Microsoft KB article. It describes a (very complicated, very technical) process for reconfiguring your computer after Office 2003 Service Pack 3 quietly disables the ability to open certain older file formats. I’m certain that my grandma can follow that to access the old recipes she typed into her computer 10 years ago, aren’t you?
I’ve been warning people for a long time about the danger of relying upon proprietary software to maintain access to archived data. If you don’t control the format or the software, there’s no guarantee that you will be able to access your data in the future. Case in point: I have a number of old school files created using Lotus Word Pro 97. I still own a copy of the software, but the only Windows operating system I have is XP, and LWP97 won’t install on Windows XP. So I have files, software to read the files, and yet I can’t get access to my own data. Presumably I could pay someone to make conversion software, but why should I pay a second time to access my data?
The church has thousands of copies and fragments of manuscripts of the New Testament. We’ve retained the ability to access the physical data (paper/papyrus is universal and long-lasting) and the format (they make me study Koine Greek), so there’s little risk of that original data being lost. But for tens of thousands of sermons written every Sunday and stored in proprietary file formats, that data may be available next week and next year, but what about ten years? Twenty? Will you still be able to access CD-ROM drives or your current hard drive? Will you continue shelling out for Microsoft Office 2017, no matter what they charge you for it? If you do, will they turn off access to your old data’s file format one day without asking you?
The solution is simple: open standards.
1. Begin thinking about how you can use open source software, which doesn’t cost any money at all, to replace closed source alternatives that will only lock you into proprietary formats. For example, use OpenOffice instead of Microsoft Office. It’s just as good as Microsoft Office for most tasks, and best of all, it’s free!
2. Save your files in ODT (OpenDocument) format, a popular open-source document format that any programmer can implement for free, so that there will always be software to open your old documents. That’s what many US states and other national governments are beginning to do.
3. Always, always keep good backups and migrate those backups to new mediums promptly so that you don’t have 5.25″ floppy disks hanging around anymore. Right now, your files should be stored on CDs and hard drives, not 3.5″ floppies, 5.25″ floppies, ZIP disks, LS120 disks, etc.
The Value of Community, or Why I Love Perl
I’ve been asked a number of times recently why I chose to use Perl to develop SAGrader, my company’s flagship essay grading product. I’ll be the first to admit that Perl tends to permit bad (unreadable, unmaintainable, overly terse) code in more ways then, say, Java. I think that those problems are mitigated by keeping to modern best practices in Perl and adhering to a coding standard, but that’s not why I love Perl. I love Perl because of the community.
SAGrader, for example, is only implemented in about 40,000 lines of code, split between actual application code, unit and acceptance tests, and HTML templates. That’s all! But if you ruthlessly reuse code from CPAN, the hub of the Perl community, you can implement computationally intelligent essay grading, a complete website to handle thousands of students, and everything else that goes on behind the scenes to make a website like SAGrader work in very little code and time. While SAGrader may only be 40,000 lines of code, we reuse almost a million lines of Perl from CPAN.
The downside of this much code reuse is that it increases the resident size of your program in memory. Frankly, memory is cheap, and programmer time, effort, and happiness is not. Perl might not be the best tool for every job, but for this job, it’s saved us (without exaggerating) man-years of time and effort.
Copyright 2006-2010 Ted Carnahan. Except where noted, the content of this site is licensed under CC-SA-BY.