Opensource vs Monosource
29 Apr 2007 Leave a Comment
in Uncategorized Tags: Programming
Sometimes freedom is not necessarily good. I’m not a man of decision-making. It would waste my a lot of time when too many dishes in the menu or too many opinions in my mind. And it’s the same in development world. In Java world, the problem is more serious. Honestly I still can’t figure, which is the best framework with less overhead in performance. Before I can sort this out, which web service I should use becomes another issue. Seems I can never start to write a line of code.
The Virtues of Monoculture – O’Reilly ONLamp Blog
Should I use iBatis or Hibernate? XFire or AXIS? Perl, PHP or Ruby? Debian, Fedora, Ubuntu or Suse? Make the wrong decision, and you can waste a ton of time, as we found out on a recent project when we wasted a week try to make AXIS2 work for a web service project, only to find out that XFire was the right choice.
Microsoft offers the certainty of no choices. Choice isn’t always good, and the open source community sometimes offers far too many ways to skin the same cat, choices that are born more out of pride, ego or stubbornness than a genuine need for two different paths. I won’t point fingers, everyone knows examples.
We spend a lot of time complaining about all the evil ways Microsoft uses to foist themselves on the world. By doing this, we automatically remove any blame that we ourselves may bear for their successes and our failures. The reality is that there are good, practical reasons that drive people into the arms of the Redmond tool set, and we need to accept that as a fact and learn from it, rather than shake our fists and curse the darkness. For we have met the enemy, and it is us, not Microsoft, at least not all the time…
Recent Comments