Perl

Superior and beutiful. I would like to hear from you reasons for disliking perl and code examples that illustrate the reasons thanks.

>>1
As a language, I like Perl very much, and use it every day. And yet it's not difficult to find snippets that make you wan't to go Hanamizawa-style on the retards who wrote them. The problem with Perl is not so much the language as the people who think they're cool just because they can write illegible code.

>>2
Who-style?

Perl is a fine language, once you understand its quirks. Readability isn't a problem if you aren't a complete dolt while writing it.

What does bother me are the troubles I've had while making ADT (things like arrays within arrays). It's much simpler in other languages.

>>1
The absolutely insane "DWIM" and "automagic" shit. No, while (<>) is not cool. No, missing parenthesis and having to guess what the fuck will it do in one or another condition is not cool. No, writing $x++ if ($x < 5); just because they botched the syntax and it won't support if ($x < 5) x++; is not cool. No, pseudo-Hungarian notation is not cool. No, backslash is a fucking ugly character and best avoided, so is -> as an operator, and don't even get me started on string comparison. No, there was no reason to change break and continue into last and next, and they sound ugly. No, $_ is not nice. No, I wanted function parameters, I don't like to have to write and maintain extra code to hack them out of a stupid list, and Python's solution is 10000x better. No, automatic global variables is not cool but the worst scope policy I've ever seen. And no, $< $| $_ $fuck don't make any sense to me. And I just mentioned the few easiest issues.

Not only you can write terrible code and Perl encourages it, but sometimes there's no other way but to write terrible code, such as functions. Everything related to functions sucks mightily.

>>5
Agreed. But as a matter of fact, Perl rocks for the simple tasks you usually choose it for and for everything else there are real programming languages. Python and Ruby are answers to questions nobody ever asked.

>>5
All your reasons except maybe function parameters are stupid and even that is not that annoying.

Automagic is very practical because it does stuff without having to specify too much what you want to do.

$@% etc is nice because you can coerce things and you know whether the type is scalar, list etc. References can be confusing especially in scripting languages. It is useful but making and referencing an array of arrays is annoying.

What exactly is wrong with string comparison?

$_ is super useful because you don't have to have a lot of annoying temporary variables.

What exactly is the problem with functions except for parameters? All a function is supposed to do is accept variables and return a value.

>>7
Also, Perl "OOP".

One word: LOL

I use perl all the time. I think it does a good job but there are many problems.

Try putting file handles in an array and going print $a[2] "FUCK";
That doesn't work.

Bareword file handles fuck everything up. The comma operator fucks shit up and makes lots of things unclear.

Many modules use stupid IO routines and don't allow you to provide your own interfaces (think proxying).

Tonnes of gay little corner cases all over the place.

No OO or namespaced interfaces to built in functions.

Dumb shit like determining if a string is a number or not.

operator overloading. lots of it is hella gay.

(format t "Perl sucks.")

>>6
Python and Ruby are real programming languages.

>>7
All your reasons except maybe function parameters are stupid and even that is not that annoying.
I'm glad you're not my co-worker, otherwise I'd have to deal with your /(#"%)"?")=(&%()= code.

$@% etc is nice because you can coerce things and you know whether the type is scalar, list etc.
Perl automatically casts "1" into int, then you come and say you want to differentiate completely different things.

References can be confusing especially in scripting languages. It is useful but making and referencing an array of arrays is annoying.
When everything is a reference, as in Python, they are simple.

What exactly is wrong with string comparison?
eq and the other stuff. I wonder why Perl people bash PHP for === .

$_ is super useful because you don't have to have a lot of annoying temporary variables.
Oh, so you save typing 4 characters of code and punish maintenance and risk bugs.

What exactly is the problem with functions except for parameters? All a function is supposed to do is accept variables and return a value.
Parameters suck more than having a nigger rape your ass as he sings rap and steals your bike all at the same time. It's like forced Python's f(*a), with an even worse syntax and no possibility of giving it a reasonable name. After knowing Python and having the flexibility of f(a, b), f(a, *b), f(**a), f(a, b, arg=val), f(*a, **b), and so on, dealing with Perl's functions is like having my balls smashed with a door. Then you have scopes. Same shit as JavaScript, what the fuck.

>>8
Oh, that too.

>>9
Oh, and I had forgotten about file handles! What kind of shit is that!? That's the worst hack ever. Magical non-dollar variables (did we need dollars after all?) that cause all sorts of trouble.

In a good, powerful language, it shouldn't matter if you're making a list of string, int, list, handle, or grandma objects.

Adding the comma operator to Perl's insane syntax is another terrible idea.

Perl lacks a file protocol/convention as Python has and a clean, nice standard library that conforms to it.

>>10
Operator overloading is actually good, as long as you use it properly. For example, it makes sense to concatenate some kind of list with "+", but it doesn't make sense to use "+" to tell a widget to accept an event. It also allows for redefining the standard behaviour of the language and use your objects instead of core objects. It's basically polymorphism, only people is afraid of it. The only difference between a == b and a.equals(b) is that  second is gay and assymetric and stupid and fugly. And you should be able to do as much of the core language as possible, and having a language where there are magical core objects with magical operators you cannot do yourself is not nice.

>>12
>Python and Ruby are real programming languages.

Keep telling that yourself.

VB.NET for the win

Real CGI programmers use assembly.

Programmers that are thinking ahead focus on Javascript and PHP.

I think by what you meant by "ahead" was without a head.

>>17
say that again in a few years when your entire operating system is merely a web browser.

>>18
Which has nothing to do with PHP as a backend, now, does it?

>>19
if you don't want it to be anything worthwhile.

>>20
If I want it to be something worthwhile, I won't be using PHP either. Get out much?

>>21
Yes because Ruby is superior? AMIRITE?

>>22
Compared to PHP, anything is superior.

>>23
Except maybe VB.

And Java

And Perl

Java > *

STOP USING BAREWORD FILEHANDLES

PERL HAS HAD MULTIPLE BETTER WAYS TO DO IT FOR AT LEAST TWO MAJOR RELEASES

>>28
tell me all about it

>>29
xterm -> perldoc, lazy bastard!

>>30
Let the Perl dudes know all tutorials still teach it the old way and nobody cares to look up the new one. Or is aware that it even exists.

What is the new way, anyway? I don't use Perl much and can't be bothered to find out myself.

Perl Way > Ruby Way > __Pythonic__

__Pythonic__ > Ruby Way >> ·$&·%"^*/
fixed

Perl rules. People who bitch about Perl are retarded faggots.

>>35 hasn't used those other languages.

alert((function(n){s="";for(i=n.search(/$/);i--;)s+=n[i];return s;})('>>36 is an idiot.'));

>>37 spends his time in the basement thinking up lame trolls.

>>37
Wins for originality and javascript:

>>35
Ever wrote anything serious?

Most of you are complete idiots. I can't believe this thread got this far.

Also in >>4 perl -e '$x++ if ($x > 5); print $x'
perl -e '$x++ if ($x < 5); print $x'
both work..