What I want to know is - can someone take Perl away from us? We all feel for tilly, but he brought us a warning. It has been mentioned in passing by several of us so far - but could it happen? Could a company (or several companies) come up and say "We own this - the language design is Larry's, the engine that implements it is ours"? Those of us hacking at the core, and core modules (we've been trying to convince people that Perl is helpless without them) need to take a look at what kind of position we're in. I think we can trust that the bad publicity this is generating, and an awareness of the strength of the Open Source community would prevent most companies from trying anything. But that's no reason to cover our butts. We can pretend that there isn't any large section of important code that a company concievably owns, but if we haven't thought about it, we don't know. I just keep thinking of the CGI mantra, "Security through obscurity is no security at all". It probably won't happen, but then I think of the GIF image format - not quite the same, but enough to scare me.
Hoping someone can calm me, and tell me it's all alright,
Erik
-
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.
|