While I grant you there are probably modules with problems, I will state for the record that I don&#x27;t consider any module that relies on specific undefined behavior that could stop functioning as expected due to a regular Perl 5 point release to be the problem of Perl 6.  If Perl 5 could break or change its functionality by changing exactly when they deal with reference counting and destroy objects, then it&#x27;s a time bomb in production anyway.<p>That said, your complaint in #2 was about Perl 6 losing to every other language in library support, but I think we&#x27;ve established it&#x27;s nowhere near as bad as that.  It&#x27;s not perfect, but it&#x27;s definitely not barren.  There&#x27;s a few tens of thousands of modules Perl 6 can try to use, and there&#x27;s a fairly good way of knowing if they will work or not, since most have good tests.<p>Your original complaint for #3 was also about companies needing to rewrite all their code.  I think Inline::Perl5 goes a long way towards addressing that as well.  It&#x27;s not perfect, but when considering &quot;Their primary motivation for staying on Perl is that they don&#x27;t want to rewrite their code. Perl 6 requires a rewrite of their code.&quot; I think it affects that point of view.<p>I think you have somewhat valid points, I just don&#x27;t think they are nearly as solid as initially presented.