On the other side of the battle, is the free loving open source hippies who are idealistic and believe software is a living entity for all to share. Google co-founders Larry Page and Sergy Brin have even published their warm and fuzzy “Do No Evil,” rhetoric at Google. At market close today (NASDAQ – “GOOG”), $464.75 per share is enough for the closed source folks to feel unsecure at night and a little intimidated.
If you are a non-techie person and you are asking this question regarding which solution better (open vs. closed source)? First, realize that whatever tech people you know, work in your company or even lie next to you at night…have already made a decision regarding their allegiance. And unfortunately, whether you know it or not, you’re already entrenched with one faction or the other. Secondly, realize that your tech people are biased if you ask their opinion. In fact, if they work with or for you, they might even flat out sabotage a change to prove they are right, thus further securing their job security, stabilizing their comfort zone, reducing their workload, minimizing their aggravation level, etc. the list goes on. If these existing tech people work with or for you…if they did not have the necessary skill set immediately (disregard whether they are capable and willing to learn new technology) are you willing and capable of letting them go? If not, stop reading… Not that it’s necessary to let people go to adopt new or different technology, but doing so is already a challenging task and you’re going to need massive help if a change is right for you.
For the philosophical sake of this article, let’s continue with some real world issues that will become the reality of some technical person whether it’s open or closed source solution. The main points are:
1. Support;
2. Security;
3. Features and
4. Scalability.
Support: Closed solution technical people typically are scarcer than open source people, thus you’ll be paying a premium to find, use and maintain them (even their training is costly). Unfortunately, most technical people are not gurus with either solution; it’s typically either one or the other. If you ask either type of person, can they learn, adopt and become experts with other solution; they will lie, steal and cheat to revert back to their preferred solution. Yes, it’s possible, but if I’m right (or even wrong) with my last statement, would you know the difference before it’s too late? Open source technical people are more abundant, cost less to maintain and replace if necessary. However, the main difference is if your technical people (with either solution) have a question or need help, close source technical people can grab a book, call an 800 support number and/or pay the vendor for help. If it is an open source solution, your technical people will turn to the Internet for forums, blogs; open sourced groups, etc. for solutions to their problems. The search engines are the sum of all human knowledge (if only they can find it!).
Security: This is a hot topic as well. Closed source evangelist will say that open source solutions are more vulnerable to hackers because the code is “open” and they can figure out the exploits. However, just because code is “closed” does not mean there are not any exploits. In fact, Microsoft (which is a “closed” system) is the most hacked software on the planet because they cannot release security patches quick enough. Tech people can tighten down security with either option.
Features: This is easy. If it’s a closed system, then right out of the box, What You See Is What You Get (WYSIWYG). There are a few exceptions to this rule (for example, how deep your pockets are), but a majority of the time, in a close solution, if it does not do what you want then either it’s too bad or you have to change what you want to conform to the closed system. With an open source system….if you can dream, communicate and/or articulate what you want, then it can be done. Closed system vendors only release software updates of features that a majority of their customers request or complain about (i.e., the squeaky spoke gets the oil) needing.
Scalability: Typically, in a closed system if you stay current with software updates and upgrades then scalability is usually never a problem. However, with an open source solution..even though customization is wide open a system of controls and documentation needs to be required of all open source technical people so that a project can continue to live on even without them. Sorry, even Jerry Garcia of the Grateful Dead died of old age (or was it too many mushrooms?).
In summary, the determining two questions are...
#1.) are you experiencing a problem that is critical to the growth or well being of your organization
and
#2.) are you on the right side?
No comments:
Post a Comment