in reply to Re^4: Elegantly map fizz to buzz
in thread Elegantly map fizz to buzz

Hi BrowserUk

I fully understand your point and appreciate it, but I have to disagree. I admit that there are a couple of things that are still obscure to me among those that I have studied, but it is really very few.

One of the reasons for such difficulties is that the documentation available is still insufficient. The official documentation is rather good (although still a bit incomplete), but sometimes it is a bit terse and you (or I) would need some further explanations, such as what you would find in the Llama and the Camel book for Perl 5, not to speak of the numerous tutorials available for Perl 5. As an example, really understanding Perl 5 references and associated data structures took me some time, but the available articles helped a lot, understanding it from just the official Perl documentation might have been more difficult.

As a relatively early adopter of Perl 6, I know that it is a bit more complicated for me than it was twelve or thirteen years ago when I picked up Perl 5, because the documentation is much less abundant, but that's OK, I expected that, and I am spending quite a bit of free time trying to help produce better documentation for Perl 6 (well, mostly in French so far, but some in English to come out soon).

But, really, Perl 6 is implementing the DWIM principle just as Perl 5, it is not difficult, you just have to pass the barrier of the (relatively few) differences between the two versions of the language. It does take a bit of efforts, but no big deal, really.

Replies are listed 'Best First'.
Re^6: Elegantly map fizz to buzz
by BrowserUk (Patriarch) on May 17, 2016 at 23:21 UTC

    Okay. But, as an example of the kind of stuff that throws my head into a loop:

    And that's just the first example. And I like concise code more then most.

    NB: I'm not wanting anyone to explain this to me; I want code to be understandable.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice.
      OK, I must say that you've got a point there. ++. And I also took you point that here is no need to try to explain it, that's not the issue.

      This is Rosetta Code, quite often the code there is very concise, almost golf. But your last example is not from Rosetta, but from the P6 documentation, so this is no excuse, and I agree that this is quite obscure.

      Having said that, there is really a lot of code out there that is easy to understand, you can read and write a lot of code without getting into what appears to be an obfuscated contest entry.