Perl is beautiful
It's just that usually people use Perl for some quick reg ex hacks and just throw some ugly code together fast to get the job done. So people just Perl on this.
Perl gives you the option to code however you want. I challenge you to post Perl code that cannot be made beautiful.
my $original = 'I want this mutated, on Perl before 5.14';
my $substituted = $original;
$substituted =~ s/want/don't want/;
print "$substituted, so I have to clone the string like a retard\n";
Also, its native arrays are retarded, and every fucking array function is destructive. The built-in exception handling mechanisms, eval and $@, are laborious and brittle, and don't get me started on that hand-wavy 'context' shit.
It does have proper lexical scoping, though, which is more than many other languages can say.
>>7
Why specify before 5.14 if it has clearly been fixed? And you have to use temporary variables in most other decent languages anyway.
Name:
Anonymous2012-10-10 19:51
>>11
what the fucking hell?
why do perl/php even exist?
Name:
Anonymous2012-10-10 19:52
>>13 BEFOREHAND: close door, each window & exit; wait until time.
open spellbook, study, read (scan, select, tell us);
write it, print the hex while each watches,
reverse its length, write again;
kill spiders, pop them, chop, split, kill them.
unlink arms, shift, wait & listen (listening, wait),
sort the flock (then, warn the "goats" & kill the "sheep");
kill them, dump qualms, shift moralities,
values aside, each one;
die sheep! die to reverse the system
you accept (reject, respect);
next step,
kill the next sacrifice, each sacrifice,
wait, redo ritual until "all the spirits are pleased";
do it ("as they say").
do it(*everyone***must***participate***in***forbidden**s*e*x*).
return last victim; package body;
exit crypt (time, times & "half a time") & close it,
select (quickly) & warn your next victim;
AFTERWORDS: tell nobody.
wait, wait until time;
wait until next year, next decade;
sleep, sleep, die yourself,
die at last
# Larry Wall
>>12
Because in the Real Word™, you sometimes have to deal with legacy crap versions of legacy crap languages. Such was my fate.
Name:
Anonymous2012-10-10 20:52
>>15
Sadly, that's true. Most distros i know have Perl 5.10 installed. And not every customer is willing to change their Perl version just for your app or because you want them to upgrade because of some syntactic sugar.
At least we have given and say in 5.10
Also, COME ON PERL6 GO GOLD ALREADY. I HATE MOOSE AND INSTALL 100's OF MODULES JUST TO HAVE DECENT OOP.
Name:
Anonymous2012-10-10 20:54
OH GOD WHY DO I HAVE TO USE A TEMPORARY VARIABLE? WHAT IS THIS SHIT? WHAT HAS BECOME OF THE WORLD WE LIVE IN?
>>16
Perl 6 won't be "gold" for a while yet, but it mostly seems to be a modules issue. I am saddened that the concurrency story is still largely unwritten, but I guess most people don't need that. Other than that, pain points:
* LWP::Simple is missing SSL (and corrupts binary streams?!)
* DBIish is pronounced like this: kav-e-at.
Fix those and I could find a use for it. I'd still have issues with concurrency and I'd have to half-ass a library for mime types.
Name:
Anonymous2012-10-10 21:26
>>7
>every fucking array function is destructive
What would you rather have shift, pop and slice do?
Name:
Anonymous2012-10-10 22:18
>>19
I would use them on copies of the array, but who uses temporary variables?
I don't understand why Perl would make me use temporary variable when no other programming language has ever required the use of temporary variables for any task at all.