note audreyt Hi. This is 唐鳳, a.k.a. Audrey Tang. For the record, I think what chromatic wrote above contains a fair and accurate assessment to <a href="http://github.com/audreyt/Pugs.hs/">Pugs.hs</a> (Perl6-on-Haskell). However, please note that it elided over our collective shift of focus to the Perl 5 runtime during 2006 on #perl6, which resulted in the first CPAN releases of <a href="http://moose.perl.org/">Moose</a>, <a href="http://search.cpan.org/dist/Module-Compile/">Module::Compile</a>, <a href="http://search.cpan.org/dist/v6/">v6-alpha</a> (now evolved into <a href="http://github.com/fglock/Perlito/">Perlito</a>), <a href="http://search.cpan.org/dist/Pugs-Compiler-Rule/">Pugs::Compiler::Rule</a>, etc. So while Pugs.hs was indeed suddenly unmaintained due to my '07 hepatitis outbreak, already by '06 we have redirected our main efforts into coding Perl6-on-CPAN. Concretely speaking, that means we took various Pugs.hs structures (Signatures<a href="http://search.cpan.org/dist/Perl6-Signature/"></a>, MetaObject logic, Grammar parser, etc) and coded <a href="http://search.cpan.org/dist/Perl6-Signature/">counterparts</a> for the Perl5 runtime. I'm very happy with what turned out - indeed <a href="http://search.cpan.org/dist/MooseX-Declare/">MooseX::Declare</a> and <a href="http://search.cpan.org/dist/perl-5.12.0/">Perl 5.12.0</a> went way far beyond our original vision, in a very good way. <hr> As for Pugs.hs, the 6.2.x series has already fulfilled its goals. In order to code the 6.28.x series (compile-time gradual typing) without unreasonable pain, it required several significant changes in the host language (Haskell). Some of them were <a href="http://hackage.haskell.org/trac/haskell-prime/wiki/Committee">codified</a> into <a href="http://www.mail-archive.com/haskell@haskell.org/msg22460.html">Haskell 2010</a> (then known as haskell-prime), such as <a href="http://hackage.haskell.org/trac/haskell-prime/wiki/PatternGuards">PatternGuards</a>; some were implemented in GHC, such as <a href="http://www.haskell.org/haskellwiki/GHC/Type_families">Type Families</a> and <a href="http://www.haskell.org/haskellwiki/Quasiquotation">Quasi-Quoting</a>. In addition to the language changes, a better theoretical understanding of <a href="http://www.haskell.org/haskellwiki/Generalised_algebraic_datatype">GADTs</a> (which was deep black magic when Pugs.hs 6.2.x first used them), of OO+Functional type inference (<a href="http://lamp.epfl.ch/%7Eodersky/publications.html">Martin Odersky</a> et al), of sound STM semantics and gradual typing (<a href="http://ecee.colorado.edu/%7Esiek/">Jeremy Siek</a> et al), was also essential in coding the type system of Perl 6 as originally envisioned. Also notable was basic groundworks for 6.28.x such as <a href="http://panicsonic.blogspot.com/2009/12/adventures-in-parsec.html">Parsec Transformers</a>, <a href="http://hackage.haskell.org/trac/ghc/wiki/SharedLibraries">Dynamic-linkable binaries</a> and <a href="http://www.haskell.org/haskellwiki/GHC/Data_Parallel_Haskell">Data Parallelism</a> (to name a few) has gradually materialized as of early 2010, so folks who'd like to tackle type systems now have a significantly easier compilation-environment support than even a year before. <hr> However, speaking for myself, though Haskell became sufficiently attractive to implement compile-time type analysis for Perl 6, the success of <a href="http://search.cpan.org/dist/Moose/">Moose</a> and <a href="http://search.cpan.org/dist/perl-5.12.0/pod/perl5120delta.pod#Pluggable_keywords">Pluggable Keywords</a> in Perl 5.12.0 has convinced me that we can also fruitfully implement such analysis directly in Perl 6, or in Perl6-flavoured CPAN modules, which is a much more straightforward way to amass a developer ecosystem than coding it in Haskell. As lambdamoose demonstrated, real programmers can write Perl 6 and/or Haskell in any language, particularly if that language is as polymorphically existentially recursive as Perl 5. :-) 835419 835731