Perl 6 -- Too Bloated to Survive? (Core Devs Discuss)

Re:Perl 6 -- Too Bloated to Survive? (Core Devs Discuss) by alanstorm on Saturday July 31, 2010 @12:15PM (#1563891)

This reminds me of a lot of the "discussion" surrounding the Mozilla project back in the pre 1.0 days.

Non Project Member makes a decent point about performance, but does so in an incredibly presumptuous, entitled, non-helpful way.

Project Members make a lot noise and had waves about pre-production, non-optimized versions, etc., but never come out and say "Yes, version n+1 of our project will most likely use more ram and run slower on the same hardware as version N of our project"

[ Parent | on HN ]

Re:Perl 6 -- Too Bloated to Survive? (Core Devs Discuss) by dasil003 on Saturday July 31, 2010 @12:31PM (#1563916)

chromatic says a factor of 2.0 is a worthwhile target (http://lwn.net/Articles/398051/). I think that's the best you'll get since good developers—especially perl6 developers—generally are copiously optimistic.

[ Parent | on HN ]

Re:Perl 6 -- Too Bloated to Survive? (Core Devs Discuss) by chromatic on Saturday July 31, 2010 @02:41PM (#1564092)

We haven't reached the point of dramatic optimizations yet. We're making some architectural changes in Parrot (the Lorito project) to allow for tracing JIT, bytecode optimizations, and slimmer deployment of dependency-traced applications.

[ Parent | on HN ]