Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others scrutinizing the Monastery: (5)
As of 2024-05-18 16:35 GMT
Find Nodes?
    Voting Booth?

    No recent polls found