Perl Monk, Perl Meditation | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I get it -- optimization is a fun game. But isn't one of the rules of Optimization Club to implement the spec first, and optimize once that's been done? One can play all day with unrolling loops, peeling away layers of indirection, and so forth to gain cycles, while piddling away time and energy that could be spent finishing the project within a timeframe that retains relevancy and the respect of potential users. A reminder: http://perl6.org/compilers/features. Red and yellow boxes indicate that time spent on optimization is premature. Spending time playing the optimization game without ever finishing the target spec is a strong indication that the project is just a toy for its developer's amusement. Does anyone outside of the project's development club care how fast it runs if it only runs a not-ready-for-production subset of the spec? I'm sorry, I have long wanted to believe that Perl6 is destined for belated success. But I'm going to have to give up that position, and resign myself to the more realistic view that it's only destined for belatedness. If you want to inspire people to regain hope and enthusiasm, and possibly even to contribute to the project, tell us that after 14 years we have something that is feature complete, and that help is now needed on optimizing performance, improving documentation, or porting extension libraries over. Update3: I do believe that those participating in the project have good intentions, a genuine interest in the project, and are involved in a thankless pursuit. So I apologize if my comments are unkind to them. I seem to be able to go days and weeks without really caring or thinking about P6. And then a post announcing and congratulating progress in an aspect of the project that seems tangential to its success comes along, and I really believe it does the project a disservice, further turning people off to it. Dave In reply to Re: -Ofun times
by davido
|
|