comment on

Ahh, I can use the riskiness of "make" to my advantage.

To what extent does the availability of source code for my product affect their risk? I would think that "availability" would greatly clear up their risks, emboldening them to take on such a task.

"The devil they know vs the devil they don't know" wouldn't be an issue any more....

Or is the reverse more likely, that with source code available, it is even less risky to "buy" because they can make/recommend/negotiate changes that expressly meet their needs?

In reply to Re: Re: software collectives vs. price of organizational license by ff
in thread software collectives vs. price of organizational license by ff

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.


Perl-Sensitive Sunglasses
	PerlMonks