http://www.perlmonks.org?node_id=1038533


in reply to Re^2: Thoughts on replacing -> with .
in thread Thoughts on replacing -> with .

For the same reasons, though on a very slightly lower scale. For very little gain, it causes a lot of confusion. Or rather would if Perl6 ever started being used and there was a chance to see and confuse Perl5 and Perl6 code.

I don't think Perl6 ever gains a reasonable sized comunity. Not because it's several years late, though that adds to the problem, but because it went completely overboard with special characters. While they "simplified" sigils (read: changed the way they worked for years) and changed the object-method "separator" to something that's kinda resembling the standard (again changing things that worked for years causing confusion), they also introduced lots of new line-noise operators and their combinations and twists.

If Perl5 looked like line noise to an unaccustomed eye, Perl6 looks like line noise even to those that love and use Perl for years.

Jenda
Enoch was right!
Enjoy the last years of Rome.

Replies are listed 'Best First'.
Re^4: Thoughts on replacing -> with .
by Your Mother (Archbishop) on Jun 12, 2013 at 18:31 UTC

    I have to say... sadly, that I agree with most of this. The -> operator being taken out rankled me quite a lot. I almost jumped into the minor list war that was going on over it and the concat op waaaaaaaaaaaaaaaaay back in the day but didn't feel qualified or entitled (since I was just following along, not doing any code/tests/etc). -> is very visual, almost like inline code flow charts.

    And I'm sorry to say this too but it's on point, even if sideways and not in reply to Jenda; I think it needs saying. If one character makes that much of a difference, one doesn't know how to type and should really put some effort into learning.