We have long faced some of the same concerns and I think I can sum up my position on open-source as a positive as...

Open-Source doesn't mean we have to develop in-house...we can hire contractors, big companies, whatever to get us a 'commercially viable' system to perform the business functions that we need, but....

At the end of the day, if the system that we have someone develop or we purchase is based on open-source technologies that gives our company much more flexibility in the long-term, which is especially desirable in an environ where companies seem to be evaporating on a regular basis.

With open-source based systems if I decide that I am unhappy with a vendor, contractor, or whomever delivered the system to me, I can fire them and hire another contractor, vendor or even move it in-house to my own group of employees if it best fits my business needs.

This is the ultimate application of the Darwin Principle to business....the companies that serve my need must do so on the merits of their abilities, not because I have become dependant on proprietary technologies they delivered to me and migrating from them would cost me more than staying...

And that, is my ten cents, my two cents is free.

In reply to Re: Re: How far Open Source has come... by phydeauxarff
in thread How far Open Source has come... by tjh

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.