Making Effective Software TCO Calculations
- Mar 24, 2006
- Inside Modern X11 Programming
- Making JavaScript Fast, Part 2
- Security in Your Pocket: OpenBSD on ARM
- Making JavaScript Fast, Part 1
- The Failure of the GPL
- How Not To Optimize
- A Half-Way Step to Apple’s Source Code: An Interview with David Chisnall
- Advanced Flow Control for Objective-C
- Erica Sadun on the iPhone SDK, OS X, and the Computing Landscape
- From NeXTSTEP to Cocoa: Erik Buck on the Development of Cocoa and Objective-C
- Fun with the Objective-C Runtime
- Marcus Zarra and Matt Long on Core Animation
- Steve Kochan on the Evolution of Objective-C
- The Technology NeXT Gave the World
- Where the Web and the Desktop Meet: An Interview with Lee Barney
- Pandora: An Open Console
- The Future of Wireless Networking
- GNU or Linux?
- Debugging C-Family Languages
- How Small Is Your PC? The Rise of Netbooks and Other Small Form-Factor PCs
- David Chisnall's CPU Feature Wishlist
- The Dynamic Languages Renaissance
- Robert Seacord on the CERT C Secure Coding Standard
- Objective-C for C++ Programmers, Part 3
- Objective-C for C++ Programmers, Part 2
- Objective-C for C++ Programmers, Part 1
- Writing Insecure C, Part 3
- Writing Insecure C, Part 2
- Writing Insecure C, Part 1
- iRex iLiad e-Reader: Linux's Answer to the Kindle?
- How It Works: Filesystems
- How the LLVM Compiler Infrastructure Works
- How It Works: Virtual Memory
- What Is C For?
- The Future of eBooks
- Imagining an Open Network
- Understanding How Xen Approaches Device Drivers
- Examining the Legendary HURD Kernel
- Competition Among Open Source Compilers
- Inside Your OS: What is a Process Scheduler, and How Does it Work?
- Bad UI of the Week: Read This (OK/Cancel)
- The End of the Desktop Era
- The What and Why of Open IM
- A Look at the Modern X Server
- The Future of Digital Media
- The Future of Identity
- Bad UI of the Week: Ask Forgiveness, Not Permission
- Copyright Versus Free Software
- Is Computer Science Dying?
- A Brief History of Programming, Part 2
- A Brief History of Programming, Part 1
- The 700MHz Question: Will the Wireless Spectrum Auction Lead to Innovation or More of the Same?
- Bad UI of the Week: The Menu Bar
- The Dark Corners of x86
- Bad UI of the Week: The Cross-Platform User Interface
- Bad UI of the Week: The Mythical "is Like" Operator
- Bad UI of the Week: Don't Make Me Tell You Twice...
- Bad UI of the Week: Kettles and Washing Machines
- The BBC iPlayer Controversy Explained
- Bad UI of the Week: The Mitten Mouse
- Bad User Interface of the Week: File It Under “Bad”
- Bad User Interface of the Week: The DVD
- A Roundup of Free Operating Systems
- DragonFly BSD: UNIX for Clusters?
- CPU Wars, Part 3: Put Your Left ARM In
- CPU Wars, Part 2: POWER to the People
- CPU Wars, Part 1: When the Chips Are Down
- ZFS Uncovered
- Vector Programming with GCC
- Free Software Versus Open Source Software
- What Programming Languages Should You Know?
- Standardizing UNIX
- Prolog: Logic Programming for Rapid Development
- POSIX Parallel Programming, Part 3: Threads
- POSIX Parallel Programming, Part 2: Message Passing
- POSIX Parallel Programming, Part 1
- The Nokia 770 Revisited
- The Open Source Desktop Myth
- Separating Style and Content: LaTeX and Typesetting
- GNUstep: A Free Software alternative to OpenStep
- Behind the Scenes of Objective-C 2.0
- The Future of CPUs: What's After Multi-Core?
- What Makes a Good Programming Language?
- Emulation: Role-Playing for Computers
- NetBSD: Not Just for Toasters
- POSIX Asynchronous I/O
- Breaking Down GPL Version 3
- The Role of Binary Drivers in a Free OS
- Security Is a UI Problem
- Debunking the Myth of High-level Languages
- A Taste of Erlang, a Dynamic, Asynchronous Message-Passing Language
- Alternatives to LAMP
- BSD Packaging Systems
- DRM: Digital Rights or Digital Restrictions?
- Introducing OpenBSD 3.9
- The Need for Virtualization and Xen
- Making Effective Software TCO Calculations
- 10 Things I Hate About U(NIX) Revisited: Readers Speak
- Comparing Open Source Licenses: GPL vs. BSDL
- BSD: The Other Free UNIX Family
- Measuring the Effectiveness of Application Security Policies
- The Cost of Free Software
- Nokia 770 Internet Tablet Week-long Test Drive
- 10 Things I Hate About (U)NIX
- The Lure of Open Source Software: Why Consider It for Your Business?
Sorry, this author hasn't posted any blogs.
Like this article? We recommend
Business and Economics of Linux and Open Source, The
In a previous article, "The Cost of Free Software," I pointed out that Microsoft was completely objective in its assessment of Windows’ TCO when compared to that of free software. Unfortunately, a bug in the way Firefox renders sarcasm caused several readers to take this statement at face value. In case this hasn’t been fixed yet:
<sarcasm>
Vendors are always completely trustworthy and reliable when quoting TCO, and would never skew statistics or select most-favorable configurations.
</sarcasm>
This being the case, it is important that an organization is able to make its own determinations as to the TCO of a system before it switches. Open source advocates are often quick to point out the lower initial cost of their systems. Detractors point to potentially higher maintenance costs. Free software advocates focus more on the freedom aspects and the associated lower cost of migration. All of these are valid points, but none of them tells the whole story. The TCO of any IT system can be broken into four components:
- The purchase price of the system
- The cost of switching to the new system
- The cost of maintaining the system
- The cost of switching away from the system
Each of these must be taken into account when pricing an upgrade.
The Initial Cost
Here free software used to have a clear advantage. At zero cost, it was a clear winner. These days, many commercial software houses have got in on the act and provide zero-cost products in areas where there is a free software competitor. Such companies aim to charge for support, and because they are the only ones with access to the product’s source code, they are the ones who can really offer this support.
Of course, the off-the-shelf cost may be only part of the story. Very often software needs customizing for a particular business use. If you are using free software then you might have more flexibility here, because you (or a contractor employed by your company) can modify the code directly, rather than having to work through a set of exposed interfaces and a bolted-on scripting language.
If you do decide to modify free software, then you either have to maintain a fork of it in-house or get your changes merged back into the main version. The first option can be expensive—you will need to pay someone to periodically merge changes from the main tree into your copy—but it can provide a competitive advantage in the short term. If you are just using the software, not building your business around it, then you lose nothing by releasing your changes, and you gain from the fact other people will help fix bugs in them. Better yet, if your required changes are useful to others, then you may be able to share the cost of having them implemented.
Account Sign In
View your cart