in reply to New Perl 6 book -- Yes, Perl 6

A good-sized chunk of the book covers Parrot, both its architecture and its assembly language. (Along with a bunch on IMCC) Even if you don't care about perl 6, it's worth at least a look-through for the parrot bits. (Standard disclaimer--I wrote one of the parrot chapters)

Replies are listed 'Best First'.
Re: Re: New Perl 6 book -- Yes, Perl 6
by Anonymous Monk on May 22, 2003 at 18:11 UTC
    Is there a ORA Parrot book in the future? (Gee, I wonder what will be on the cover?). Hopefully, there will be a mod_parrot book one day. Why a book now? Is ORA paying you all well, so you can devote more time to development? I also hear there will be more articles in Linux Mag forthcoming. Is all the publication a way for the developers to get much needed funds?
[reply]
      There's probably a Parrot book in the future, though that's not certain. (Cool though it might be, there's a limit to the size of the market for internals-level books for most any product) Whether there'll be a mod_parrot book depends on both the existence of a production mod_parrot and demand for a mod_parrot book. Personally I hope so, but we'll see.

      Ora's paying Allison, Leo, and I standard royalties (with 20% of the author royalties going to The Perl Foundation, and O'Reilly's matching that) so if past book history in general is any indication, we'll end up getting billed rather than get cash. There's the ineffable sex appeal of being a geek book author to balance that, though. :)

      There is, or rather was, a set of articles in Linux Magazine. (And thanks for reminding me--I need to check and see if they paid) The April issue had a Parrot article I wrote and a Perl 6 article that Damian wrote in it.

[reply]
        we'll end up getting billed rather than get cash
        Sigh. Does that happen often? I was under the impression that authoring ORA/Perl/programming books didn't pay well, but was still a net gain; seems I wasn't entirely correct.

        Next time I hear of someone pirating ORA books, I think I'm going to be more hard-nosed about it.

        Perl programming and scheduling in the corporate world, as explained by dragonchild:
        "Uhh ... that'll take me three weeks, broken down as follows: 1 day for coding, the rest for meetings to explain why I only need 1 day for coding."
[reply]

In Section Perl News