|
|
Subscribe / Log in / New account

Ideas versus implementation

Ideas versus implementation

Posted Jul 22, 2017 21:00 UTC (Sat) by ssmith32 (subscriber, #72404)
In reply to: Ideas versus implementation by excors
Parent article: Ideas versus implementation

Note, though, the different emphasis of the comments - "user friendliness" vs "easy to write". A lot of people using Perl scripts, did not write the original code base - most of their work in Perl would be reading it and tweaking it. Or, more likely, reading it for hours to get an idea of what it does, running it a few times to make sure, and, if you're lucky, it's simple enough to just rewrite the mess, otherwise, wrapping it up in another script, because it's easier.

Now, I have come across a Perl script or two that was nice and clean and understandable, but those are exceptions.

If there ever was such a thing as a write once, read never medium, Perl is it.
This is the downside of "I can program like C for a while, except for these few lines that look like bash, and another few lines that are just some idiom unique to Perl", all mushed together.

So it depends on what you mean by user...


to post comments

Ideas versus implementation

Posted Jul 27, 2017 10:35 UTC (Thu) by niner (subscriber, #26151) [Link]

The difference may be between Perl scripts - often written by individual sysadmins and other non-programmers - and Perl applications written by teams of software engineers who actually care about maintainability, have coding guidelines, tests, etc. I usually deal with the latter and we've yet to come across a new team member for whom code readability was an issue. And they are usually Perl beginners as it's quite hard to hire experienced Perl developers here.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds