Except that huge corporations use both Perl and Common Lisp on a daily basis. Craigslist, Google, etc.<p>So you have some old perl scripts laying around, but they work well enough and some guy takes care of them, updating them when they need. He knows perl and that&#x27;s his job, so whatever. One day, the architecture changes and the scripts need to go parallel. That&#x27;s a problem because the perl guy doesn&#x27;t know Pony (a promising language with a community even smaller than perl6...) and really needs to get these scripts running again.<p>So he uses Perl6 along with the inline module, and things are working again. Over time, he hacks up a better system in vanilla Perl6, and deploys that too. He had such a great time using Perl6 that he even hacks up a few more tools he could use, etc etc, next thing you know he&#x27;s a Perl6 developer.<p>I write ruby because it is modeled similarly to how I think about problems, but if I was a perl guy, I could see the appeal to Perl6, but saying that it&#x27;s a dinosaur is both wrong and irrelevant to the FUD surrounding Perl6 right now. At this point, it&#x27;s about adoption.