I never buy the "many keystrokes" argument, for Perl or Java or AppleScript or anything. Editors for programming have been around for a LONG time. Learn to use them effectively, as they will compensate for any lack of typing skills or energy. Autocompletion tools are not a new science. Notepad is not a programming editor.
I will argue the companion point, but this again is not just Perl: way too much syntax in most of the code I see. Too much ->{} and ${@{$$x}} and \($!) in high-level code. People get in the habit of typing while they're thinking in terms of the implementation, instead of thinking in terms of expressing the solution to a problem.
I try to write my libraries such that the caller doesn't have to write a lot of syntactic noise just to get things done. In other words, the lower level code should take it on themselves to make literate programming possible at the higher levels.
--
[ e d @ h a l l e y . c c ]
| [reply]
[d/l]
[select] |
Many keystrokes when working with files? Ever had to do anything file related in VBScript? That's what I call many keystrokes. Set FS = Server.CreateObject("Scripting.FileSystemObject") anyone?
Jenda
|
XML sucks. Badly. SOAP on the other hand is the most powerfull vacuum pump ever invented. |
| [reply]
[d/l] |
you're right: perl is better than VBScript.
But it is worse than perl6, where it is allowed to do my $contents = "filename".slurp;
Currently there are limitations, but moving to right direction :)
| [reply]
[d/l] |