in reply to The sad state of Perl documentation
And opinions filled the room...
I may as well add a few things:
man / perldoc:
These are not intended (for the most part) to be a tutorial. If you want to learn, you buy a book, like with most other things. Perldoc is however an excellent reference manual. It's not very useful until you actually know perl. On the other hand, when you DO know perl, it is an excellent place to "look something up". The great advantage is that practically everyone installs perldoc along with perl. If you program perl, you always have perldoc. It is however , in my humble opinion, utterly useless when printed. The sections are HUGE and quite impossible to navigate without some form of search/matching. Furthermore, it is nice to know that perldoc is up to date. I do not consider this sad. As soon as you buy a book or print a reference manual, it will become old.
Postscript:
This is not only very common on UNIX platforms. It is also quite common on other systems such as Windows. Printers really like PostScript.
So, following some form of logical deduction, one might say that PostScript is a good format to store text in, if it is intended for printing. This causes no problems, as it can also be viewed with a variety of programs.
) However, following some form of illogical deduction, Windows does things a bit differently. It uses PS. A lot. There are however few programs that can display a simple PS file. Instead they have choosen to use every other format imaginable to store files, ready for printing. They use rtf, doc, pdf and and a variety off odd (and always commercial) formats. This strikes me as very odd. Having dozens of non-free formats that do the exact same thing is not a bright move. Even more so as the first thing that happens when you print it, is a conversion to PS, so the printer will understand it.
I may as well add a few things:
man / perldoc:
These are not intended (for the most part) to be a tutorial. If you want to learn, you buy a book, like with most other things. Perldoc is however an excellent reference manual. It's not very useful until you actually know perl. On the other hand, when you DO know perl, it is an excellent place to "look something up". The great advantage is that practically everyone installs perldoc along with perl. If you program perl, you always have perldoc. It is however , in my humble opinion, utterly useless when printed. The sections are HUGE and quite impossible to navigate without some form of search/matching. Furthermore, it is nice to know that perldoc is up to date. I do not consider this sad. As soon as you buy a book or print a reference manual, it will become old.
Postscript:
This is not only very common on UNIX platforms. It is also quite common on other systems such as Windows. Printers really like PostScript.
So, following some form of logical deduction, one might say that PostScript is a good format to store text in, if it is intended for printing. This causes no problems, as it can also be viewed with a variety of programs.
) However, following some form of illogical deduction, Windows does things a bit differently. It uses PS. A lot. There are however few programs that can display a simple PS file. Instead they have choosen to use every other format imaginable to store files, ready for printing. They use rtf, doc, pdf and and a variety off odd (and always commercial) formats. This strikes me as very odd. Having dozens of non-free formats that do the exact same thing is not a bright move. Even more so as the first thing that happens when you print it, is a conversion to PS, so the printer will understand it.
In Section
Meditations