<?xml version="1.0" encoding="windows-1252"?>
<node id="982547" title="Four Legs Good, Five Legs Bad" created="2012-07-18 18:07:45" updated="2012-07-18 18:07:45">
<type id="11">
note</type>
<author id="1382">
chromatic</author>
<data>
<field name="doctext">
&lt;blockquote&gt;&lt;em&gt;... calling Perl 6 "production ready"...&lt;/em&gt;&lt;/blockquote&gt;

&lt;p&gt;If you call a tail a leg, how many legs does a dog have?&lt;/p&gt;

&lt;p&gt;It doesn't matter what you call Perl 6. The fact of it is that, for the foreseeable future, deploying a Perl 6 application will require you to follow the Perl 6 development process pretty closely. Sure, you can get a lot done with the state of either of the two leading implementations&amp;mdash;if you're willing to invest the time in an immature product. Sure, there's a renewed commitment to improving the maturity of Rakudo at least.&lt;/p&gt;

&lt;p&gt;Those are all well and good, but a tail is still a tail and not a leg.&lt;/p&gt;</field>
<field name="root_node">
982112</field>
<field name="parent_node">
982529</field>
</data>
</node>
