But I clearly remember the first stabbing pain that told me it was going to be something different than first advertised.
I confess I don't quite understand this. Than first advertised by
whom? As far as I'm concerned, the first advertisement for Perl 6 was simply that we were going to look at Perl as a community and fix everything that needed fixing, and that it would certainly include making Perl powerful enough that we could write its parser in Perl itself. If things have changed from that, it's perhaps a sense of reality about how
many things there were to fix. I expected maybe 20 RFCs, and we got 361. Our eyes were opened to the fact that pretty much everyone had tunnel vision about how to change Perl for the better, and that the sum of the community's pain was much greater than any individual piece of it. To me, we are still precisely on the originally announced target of having a community rewrite of Perl. We just didn't understand the scale of what that meant.
We also didn't understand the full ramifications of what it means to have a Perl 6 compiler written in Perl 6. Among other things, it means you don't really have to care whether the backend is using Haskell or Parrot or the latest and greatest VMs from MS and Sun. The current Haskell implementation of pugs is a nice prototype, but in the long run, Haskell is just another engine to run on.
As mentioned elsewhere, fglock has already bootstrapped a mini-Perl 6 in itself. And we're a goodly part of the way to having a full Perl 6 parser written in full-up Perl 6. See the standard grammar, which we can currently parse, but not quite run yet. But it's getting there. (Would you trust a precompiled compiler written in Perl 6?) Once we get to the point of being able to run it (on any of the engines), things will converge rather rapidly from there on.