<?xml version="1.0" encoding="windows-1252"?>
<node id="992765" title="Re^3: Metrics tracking Perl 6 development" created="2012-09-10 09:55:04" updated="2012-09-10 09:55:04">
<type id="11">
note</type>
<author id="616540">
moritz</author>
<data>
<field name="doctext">
&lt;blockquote&gt;Is Perl 6 at least as much production ready as much as Perl 5 is?&lt;/blockquote&gt;

&lt;p&gt;For what use cases?&lt;/p&gt;

&lt;p&gt;You see, Perl 6 isn't meant as a successor for Perl 5 (at least not anymore; that was the original intention for Perl 6, but we've diverted from that path long ago), so it's not clear to me that Perl 6 has to excell in exactly the same spots as Perl 5. So I don't think we need to have a complete superset in productivity to declare it production ready.&lt;/p&gt;

&lt;blockquote&gt;That question captures what people mean when they ask for production readiness of Perl 6.&lt;/blockquote&gt;

&lt;p&gt;Citation needed. Maybe it captures your idea, but people I talk to all have different ideas of production readiness.&lt;/p&gt;

&lt;blockquote&gt;That question captures what people mean when they ask for production readiness of Perl 6.&lt;/blockquote&gt;

&lt;p&gt;I frankly admit that on most areas, existing Perl 6 compilers cannot compete with Perl 5 on most "production readiness" metrics. So, if that's the answer you want to hear, please have it and be happy.&lt;/p&gt;

&lt;p&gt;But there are a lot of folks who don't need the same level of stability and speed, and who are willing to give up a bit of both in exchange for a much more expressive and consistent language. And for those folks we need a more detailed answer than "yes" or "no". It's for those folks that we blog about our progress, fix bugs, add features and make monthly releases -- not for the anonymous crowd waiting for a release labeled 1.0&lt;/p&gt;

&lt;!-- Node text goes above. Div tags should contain sig only --&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-616540"&gt;
[http://perl6.org/|Perl 6 - the future is here, just unevenly distributed]
&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
992603</field>
<field name="parent_node">
992700</field>
</data>
</node>
