Perl looks ugly to novices?

I thought the whole point of Perl was that there were so many ways to code something, there's always a way to make the code look elegant.
From Larry Wall:
Perl is designed to give you several ways to do anything, so consider picking the most readable one.
This contrasts languages like Ruby which basically encourage/force you  to do things a specific way.

Just read this quote
I have a pretty major problem with a language where one of the most common variables has the name $_
Except you never have to use $_ in the first place. It's always a choice

In conclusion, people who don't like Perl don't know how to use it.

>>16
Good then. I hope contribute good written code. What I am attacking is mainly that you can do one thing well in any compiled language, and in Perl you can do it 100 ways. The reason stems from the language being mostly syntatic sugar.

I agree, the language is awesome when you have programming experience. It saves time when you only have to use N amount of macros for what you need, an deploy a quick solution. And it is why the language is adored in business.

However, you and I know that the next person will not be able to read the macros, and debugs errors that stem from virtual functions, because you must learn the other's person macro language. More time is dedicated on reverse engineering Perl code that has already grown for entire servers interfaces or applications, than optimizing.

However the subject is readability. If we are talking about eyes, I listed the in order the ones you need. If you need abstracts, I listed those too (not in order).

Above all, I am great believer on doing something right the first. But above all, optimization.

I believe we had a thread about this, the shittyCase one. Ah:
https://dis.4chan.org/read/prog/1344869235
>>11

night