<div dir="ltr">well, there 2 main issues:<div>1. legal<div>big corporates have difficulty handling the open-source type of licenses. </div><div>and since any legal issue can end up costing millions in fees or court issued</div>
<div>penalties. the company tend to frown upon using such tools.</div><div>2. stability</div><div>some common CPAN modules are not very reliable.</div><div>for example: threads. although it is great and i love using it, there is almost</div>
<div>no support, and we encountered bugs that due to schedule issues forced us to </div><div>abandon threads all together and develop solutions using other mechanism (fork for example)</div><div><br></div><div>as an open source developer, i use perl and CPAN modules as much as possible. i love it.</div>
<div>it gives me great flexibility and saves me a lot of coding time. however, from the corporate</div><div>point of view. this is horrible.</div><div><br></div><div>--</div><div>Ronen<br><br><div class="gmail_quote">On Wed, Nov 24, 2010 at 11:33 AM, Gabor Szabo <span dir="ltr">&lt;<a href="mailto:szabgab@gmail.com">szabgab@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Wed, Nov 24, 2010 at 1:06 AM, Ronen Angluster &lt;<a href="mailto:beerholder@gmail.com">beerholder@gmail.com</a>&gt; wrote:<br>

&gt;<br>
&gt;<br>
&gt; On Tue, Nov 23, 2010 at 9:46 PM, Gabor Szabo &lt;<a href="mailto:szabgab@gmail.com">szabgab@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Tue, Nov 23, 2010 at 5:33 PM, Ronen Angluster &lt;<a href="mailto:beerholder@gmail.com">beerholder@gmail.com</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt; &gt; i can&#39;t use Moose cause of legal &amp; corporate issues. lets not dwell on<br>
&gt;&gt; &gt; this,<br>
&gt;&gt; &gt; its a life fact<br>
&gt;&gt; &gt; and we came to peace with it.<br>
&gt;&gt;<br>
&gt;&gt; Does the corporate policy forbid anything from CPAN or only Moose?<br>
&gt;<br>
&gt; as a thumb role, we prefer not to introduce any new CPAN modules into the<br>
&gt; system.<br>
&gt; the &quot;cost&quot; of such actions dictate that we should strive to build things<br>
&gt; in-home<br>
<br>
</div>So this is an area where the open source developers and the people in<br>
the company<br>
you work for disagree. AFAIK most of the people in the open source community<br>
would want to reuse code from CPAN where possible.<br>
As my objective is to try to bridge the gap between the companies and<br>
the open source<br>
community I&#39;d like to understand where does this difference come from?<br>
What &quot;costs&quot; do you see that the open source developers don&#39;t see<br>
and code developed in-house does not have?<br>
<br>
regards<br>
<div><div></div><div class="h5"> Gabor<br>
_______________________________________________<br>
Perl mailing list<br>
<a href="mailto:Perl@perl.org.il">Perl@perl.org.il</a><br>
<a href="http://mail.perl.org.il/mailman/listinfo/perl" target="_blank">http://mail.perl.org.il/mailman/listinfo/perl</a><br>
</div></div></blockquote></div><br></div></div></div>