|
|
Recent Articles |
Java Programmer – Common Scoping Errors
Scoping errors comes in various sizes and shapes. Novice Java programmers most often commit some silly mistakes which are undesirable.The most common mistake novice programmers commit is scoping errors which comes in many ways.
Preparing For Your SCJP Exam
The SCJP 310-065 exam is not easy to crack. I have an experience of using the UCertify's SCJP 310-065 exam preparation kit for quite a long time,and it is needed the best exam preparation kit available. I have...
The Truth Of Being Sun Certified
Being a Sun Certified Java Programmer(SCJP) is undoubtedly a matter a pride, But due to the immense increase in qualified Human Resource especially in IT/ITES sector, it is no longer a matter of pride. Once upon a time (2-3 years back) we knew that...
Preparing For Your Windows Server...
Note: These instructions are for Microsoft Windows Servers. Linux or Apache 301 Redirect Instructions can be found here.
Redirecting pages on a Windows Server can be complex, but it is still highly recommended...
|
|
10.02.09
| Identifying Differences In Open Source And Open Standards |
 By Savio Rodrigues
Reading Michael Tiemann's notes for his Open World Forum speech I can't help but think that he's attributing a point of value to open source that is much more aligned to open standards based software.
Tiemann writes:
"Lately, I have seen an increasingly important and new implication even beyond what Corey Doctorow has said about free when it comes to software: when the cost of acquisition goes to zero, the cost of retirement (aka "exit cost") cannot be ignored."
Tiemann goes on to suggest that the cost of exit for open source software is lower than proprietary software. That can sometimes be true. But open source is no panacea for exit costs. Open standards, while no panacea either, are orders of magnitude more helpful at reducing exit costs than open source by itself.
Let's say I'm using an open source administration and management product, or an open source content management system and want to migrate to an alternative. How easy will that migration be? Compare with migrating in either direction from GlassFish Application Server to Apache Geronimo. The latter will be easier because both products are standards compliant with the JEE specifications. It goes without saying that open source isn't a necessary condition to being standards compliant. I'd argue that the cost of exit for standards based software, open source or proprietary, is on average, equal or lower than the cost of exit of open source software around which there are no overarching standards. I don't have hard data to prove this point. However, I do know that CIOs making middleware purchase decisions are keenly interested in reducing vendor lock-in through open standards.
I'm not alone in disagreeing with Tiemann's views on software exit costs. Open source business intelligence vendor Pentaho's James Dixon writes in response to Tiemann:
"...true that it might sometimes be easier to get your data out of an open system but most proprietary vendors have migration tools to help move data into their system from a competitors – and of course pre-sales engineers to help out."
Again, while standards aren't guarantees of seamless migrations and lower exit costs, standards do however ease the burden. If only open standards were given the same spotlight that open source receives.
Comments
About the Author:
Savio Rodrigues is a product manager with IBM's WebSphere Software division. He envisions a day when open source and traditional software live in harmony. This site contains Savio's personal views. IBM does not necessarily agree with the views expressed here.
|
