After a few hiccups, I downloaded Rakudo yesterday on my Macbook and was able to run a couple of tiny programs. Where to from here? But, I am getting ahead of myself.

Yesterday, I signed up for and attended a Python "bootcamp," probably the only way I will force myself to learn that language. My impression after the first day, meh. There are a few things that I like (all variables are objects), and many things that I dislike. Yet, nothing compelling that says I should use Python. Of course, from just empirical observation, Python seems to be doing quite well in programs that require an interface, and has a rather useful shell and editor. Of course, it doesn't have anything quite like CPAN. So, after the first day of Python, I decided to learn more about Perl6, and discovered last night that Perl6 is indeed real, and it addresses most of the gaps vis a vis OO. Its ability to create programs that have interfaces remains to be seen, especially in how well it will allow one to interface with native GUI tools... something like the old Camelbones project would be nice. Create the interface using Interface Builder (on the Mac), and write the code that runs it in Perl.

Now, a few Perl6 specific questions --

  1. Is there a http://perldoc.perl.org/ analog for Perl6? Finding even a list of methods supported by objects was tricky. Absence of $str.length confounded me for a while.
  2. Are there tutorials other than at http://svn.pugscode.org/pugs/examples/?
  3. Is it really necessary for perl Configure.pl --gen-parrot to use svn https://? My svn was compiled without secure http support, so that led me on a wild goose chase to first upgrade svn. Why is it necessary to use https? Additionally, why download the code using git, and then fire Perl to download whatever it downloads using svn... are two version control systems really needed? I guess, what I am saying is, make it as easy as possible for folks to get started. There may be many who are curious about Perl6, and would like to start off as easy as possible. In fact, perhaps the best thing would be if there could be a Perl6 implementation within a browser, much like Ruby has on its website. That way one could try out the latest Perl6 without even installing it.
  4. The distinction between Parrot and Perl6 seems really confusing. Is Parrot wasting a lot of effort trying to be a compiler for a host of languages? What benefit would there be to creating such a universal compiler? Would the development of Perl6 itself be faster if Parrot focused only on Perl6?
What I have seen thus far looks really exciting. My final question is -- when will a production ready version of Perl6 arrive?

And, finally, my thanks to all those who have worked and are working on Perl6. Really, I mean it.

--

when small people start casting long shadows, it is time to go to bed

In reply to Starting with Perl 6 by punkish

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.