Comments on: Why Buy the Cow When You Can Get the Milk for Free? http://exitcondition.alrubinger.com/2008/02/24/why-buy-the-cow-when-you-can-get-the-milk-for-free/ Andrew Lee Rubinger Thu, 03 Dec 2009 00:40:14 +0000 http://wordpress.com/ hourly 1 By: d1kk http://exitcondition.alrubinger.com/2008/02/24/why-buy-the-cow-when-you-can-get-the-milk-for-free/#comment-22 d1kk Mon, 25 Feb 2008 19:12:40 +0000 http://exitcondition.wordpress.com/?p=14#comment-22 Very good article. alrubinger, not bad :) Very good article.
alrubinger, not bad :)

]]> By: alrubinger http://exitcondition.alrubinger.com/2008/02/24/why-buy-the-cow-when-you-can-get-the-milk-for-free/#comment-21 alrubinger Mon, 25 Feb 2008 16:07:54 +0000 http://exitcondition.wordpress.com/?p=14#comment-21 Ivan: At first glance, SpringSource. Getahead's DWR. Any company that sponsors/leads an open source project and provides reliable support contracts. I've probably drawn a thin line here between "Professional" and "Web 2.0-type" Open Source, in my decision to exclude vendor names from attack in an attempt to keep this post non-political. But looks like that can't be avoided. So where can I place Google technologies, like GWT and Guice? Apache's HTTPD, Tomcat, Commons? Sure, the ASF is kind of in no-man's land here, as there are a series of mature, stable products under their umbrella. However, Apache's not really in the business of business as much as their intent is to provide a secure environment in which open source developers may contribute. Bottom line is, you've gotta identify which solutions have an active community and available support/training systems, even if offered from a qualified 3rd party. My intent here is to point to the benefits of Open Source as a viable base, not to slam free software that comes without warranty. My tongue-in-cheek Web 2.0 Category is reserved for projects that cater more to easing development for the unseasoned programmer than providing real-world functionality. S, ALR Ivan:

At first glance, SpringSource. Getahead’s DWR. Any company that sponsors/leads an open source project and provides reliable support contracts.

I’ve probably drawn a thin line here between “Professional” and “Web 2.0-type” Open Source, in my decision to exclude vendor names from attack in an attempt to keep this post non-political. But looks like that can’t be avoided.

So where can I place Google technologies, like GWT and Guice? Apache’s HTTPD, Tomcat, Commons?

Sure, the ASF is kind of in no-man’s land here, as there are a series of mature, stable products under their umbrella. However, Apache’s not really in the business of business as much as their intent is to provide a secure environment in which open source developers may contribute.

Bottom line is, you’ve gotta identify which solutions have an active community and available support/training systems, even if offered from a qualified 3rd party.

My intent here is to point to the benefits of Open Source as a viable base, not to slam free software that comes without warranty. My tongue-in-cheek Web 2.0 Category is reserved for projects that cater more to easing development for the unseasoned programmer than providing real-world functionality.

S,
ALR

]]> By: Ivan http://exitcondition.alrubinger.com/2008/02/24/why-buy-the-cow-when-you-can-get-the-milk-for-free/#comment-19 Ivan Mon, 25 Feb 2008 07:02:33 +0000 http://exitcondition.wordpress.com/?p=14#comment-19 what technologies other than JBoss would you call "professional open source" according to your breakdown? what technologies other than JBoss would you call “professional open source” according to your breakdown?

]]>