On Mon, Jun 27, 2016 at 8:11 AM, Parrot Raiser <1parr...@gmail.com> wrote:
> We should all be thinking about the "killer application" for Perl 6; > the sort of job that is made so much easier by it that people will > overlook all sorts of problems. > Look towards the kinds of problems being solved by Go and Python in the parallel (message passing and tight smp)/distributed/scientific computing space. As Larry pointed out in his YAPC::NA Q&A, he wanted to make things like PDL easier and more naturally expressed in the available language features. Similarly, Damian pointed out in hist keynote how natural it was to express scientific ideas in Perl 6. Providing development tools, in particular static-ish analyzers for Perl 6 *and* Perl 5 (among other languages) might also be a rich area to explore. Time spent on CMS software and replicated tired applications is going to a waste of time (though not the framework(s) to make creating them easier). Brett > > On 6/27/16, Kaare Rasmussen <ka...@jasonic.dk> wrote: > > Hi List > > > > Now that 6c is 6 months old, I'm wondering if there is any sign of Perl > > 6 adoption in companies, startups, etc for professional use? > > > > It may be premature to expect any widespread professional use, but I > > would like to know more about what ecosystem we have. With > > "professional" I don't refer to the code quality, but if anybody is > > seeing Perl 6 as giving them a business advantage. > > > > /kaare > > >
