Where better to talk about this than here? I feel something that's been bugging me for a while that's very much Perl related, so I post it. It seems to me that it's rather hard to meditate about anything in Perl that hasn't been rehashed somewhere or another.

I can only assume that Merlyn still has issues with the subject, or else he wouldn't refer to it on his homepage in such a bitter fashion. I could care less about the particulars of why. What is wrong is wrong. I cannot think of a reason to justify treating an author in such an orwellian fashion.

Right now I'm sitting next to a book shelf crammed with 36 volumns of O'Reilly books. Another ten are waiting for me at my desk at work. I have always been a true lover of their work. (Except for ASP in a Nutshell and that MySql & mSQL edition. Bleach:-P) Still, Perl is not a trademark of O'Reilly and Associates. When one of the native sons of that community is treated in an unjust fashion by a company, shouldn't another member of that community voice his indignation if he feels it?

As far as I'm concerned as long as O'Reilly continues to not give him credit for his work people should be reminded of their actions.

Thank you for your perspective. I truly appreciate it.

()-()
 \"/
  `                                                     

---

---

• 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.