<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ralph</author><text>I sought permission from Tim O&apos;Reilly, he co-wrote this back when he was an author, to re-enter the text of the book as troff source, the original being lost. He kindly gave it and volunteers from the groff@gnu.org mailing list split the chapters amongst themselves; it was quite fun. &lt;a href=&quot;http://home.windstream.net/kollar/utp/&quot; rel=&quot;nofollow&quot;&gt;http://home.windstream.net/kollar/utp/&lt;/a&gt; is the result.</text><parent_chain></parent_chain></comment><story><title>Unix Text Processing (1987)</title><url>http://oreilly.com/openbook/utp/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>kamaal</author><text>A very nice book available for free. It makes me very happy that I can learn new ways to do my work smarter.&lt;p&gt;Some of the best known advantages of Unix text processing tools is, as long as you can reduce your problem to &apos;Text&apos;- There exist some very powerful, succinct and quick solutions to even some very difficult problems.&lt;p&gt;Well it takes some time to get a grip on how to work with Unix text processing utilities and tools like Perl. Once you are upto speed, you see how much work you can do so quickly with so much little effort. In fact the more you get into it, you realize how much useless code you have writing over the years. While all you needed was a command with a few options.</text><parent_chain></parent_chain></comment><story><title>Unix Text Processing (1987)</title><url>http://oreilly.com/openbook/utp/</url></story>