On one hand, I'm happy you found something more productive.
On the other, I've spent a good chunk of time just reading other people's code, and I've come to appreciate really straight forward verbose code.
So I am a bit biased against the Perl I've seen, since it is generally not written with ease of understanding as a priority.
Re:Java Pain
by yellowapple on Monday June 30, 2014 @01:38PM
(#7966364)
That's unfortunate. I try to keep my code (no matter what language, Perl included) as readable and tidy as possible for the sake of those reading the code in the future (myself included). While creatively stringing an incomprehensible stream of punctuation marks into a usable program is fun, I'm with you in agreeing that such coding styles should be avoided in anything that's not a one-off mental exercise.
That said, too much verbosity can introduce the same problem of unreadability by making important things harder to identify. There's an important balance between verbosity and terseness that should always be considered.
Re:Java Pain
by peterashford on Monday June 23, 2014 @08:28PM
(#7935584)
HTTP should be secure. A programmer should have to go out of their way if they want something designed to be secure to act in some other way.
"Easy things should be easy, and hard things should be possible." -- Larry Wall
One of the reasons why I switched from Java to Perl. I didn't feel that easy things were easy in Java, and I don't run into enough hard problems on a daily basis to justify the verbosity and masochism involved.