We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
80,259 News Articles

Analysis: The big problems with open source

We look at the cons rather than the benefits

Tight budgets prompt another look at open source. Users say savings and other benefits are easy to reel in, but there are problems, too. We take a look at just what you need to consider with open source.

At the New York State Office of Temporary and Disability Assistance, Chan is creating a direct comparison between the cost and performance of the new IT environment and the older one.

He cautions that it requires an investment of resources to run tests and create meaningful benchmarks.

And even if you're only planning to use the software internally, it's important to ensure that the legal department understands the numerous types of licences available, Driver says.

"Restrictions vary, sometimes dramatically," he says.

"You don't want to get a letter from your lawyer with an injunction because your open-source solution violated someone else's intellectual property."

Fitting open-source technology into your current infrastructure is another thorny issue.

Three years ago, Roy Mentkow, director of technology for Roanoke in Canada, decided to transition from Microsoft Office to OpenOffice.

However, for some users, desktop applications were heavily integrated with Lotus Notes workflows.

"We had to ensure OpenOffice worked well with Notes on an application-by-application basis," Mentkow says.

"That was something that snuck up on us."

In the end, the city migrated about half of its 900 users, resulting in $140,000 in savings.

Still, Mentkow says, the savings won't come all at once but rather when those desktops would have been upgraded to a new version of Microsoft Office.

It's also important to look beyond another widely touted benefit of open-source software: the ready pool of developers who are familiar with the technology and see the prospect of using it as a retention or hiring plus.

While it's true that developers are plentiful and eager to work with open source, that expertise can come at a price.

"If you asked a developer if they'd like to work with open-source or commercial software, eight times out of 10 they'll say open source," Lyman contends.

And some developers may charge less than developers who work with commercial products.

Hamadeh says that with SugarCRM, it's even possible to "have a local student come in and program something in a couple of hours," Hamadeh says, or a tech-savvy business person can create custom modules.

But, he cautions, while there are some SugarCRM consultants who will do a great job, they can be expensive, so having internal IT talent can help you avoid added costs.

Brisbin points out that the success of open source at NPC is due largely to the fact that its developers have a breadth of knowledge and are willing to work outside of narrowly defined silos.

"We have small development teams, and we cross areas of responsibility," he says, noting that he routinely moves among RPG, Java, web front-end development, PostgreSQL and the underlying application system.

"There is a critical mass of information you need to have as a developer to do open source effectively," Brisbin adds.

And then there's one of the more hard-to-quantify costs: cultural change. Mentkow says Roanoke's move to OpenOffice involved changing the culture as much as it did changing the desktops.

"Cultural change does not happen in moments," he says.

"As we move to different platforms and different standards, what we have to see is an acceptance of those changes."

Sims adds that it's easier to achieve cultural change at organisations that value resourcefulness and courage, since moving to open source represents a break from the approach that involves seeking traditional answers to difficult problems.

"People still say you can't get fired for buying Microsoft or Oracle - how about, you should get fired for not coming up with the best scenario that meets your company's unique criteria, regardless of conventional wisdom," he says.

As open source matures, companies will begin to get past the misconceptions, understand the implications and balance the benefits with the downsides.

"Most of the time when there's a problem, it's because there's an assumption of 'It works, and when it doesn't, we'll fix it ourselves or find the answer on the internet,' " Driver says.

"Or there's an assumption that the cost of acquisition can be extrapolated to total cost of ownership. But there's a care and feeding cost to everything."

NEXT PAGE: Adaptable open source

  1. We look at the cons rather than the benefits
  2. Not always open
  3. Support costs
  4. The need for investment
  5. Adaptable open source

IDG UK Sites

Best camera phone of 2015: iPhone 6 Plus vs LG G4 vs Galaxy S6 vs One M9 vs Nexus 6

IDG UK Sites

In defence of BlackBerrys

IDG UK Sites

Why we should reserve judgement on Apple ditching Helvetica in OS X/iOS for the Apple Watch's San...

IDG UK Sites

Retina 3.3GHz iMac 27in preview: Apple cuts £400 of price of Retina iMac with new model