I agree. Such is the blessing and the curse of the community-based product. I too feel the depreciating excitement of the arrival of Perl6 as time goes by. Though I have in part switched to C# for certain implementations, Perl still has a unique productivity efficiency, though it is not easily recognised by those looking in from the 'outside'.
I am very happy that ActiveState is providing excellent binary support for the Windows users, which I am a part of (though not exclusively). Through the ppd I am able to set up my web app framework with relative ease. Moving forward, how does ActiveState take to the idea of supporting emerging Perl-based projects? Some ideas: 1. PDK makes writing Windows services and binary packaging relatively easy. Unless I am missing the picture somewhere, the act of writing a full-GUI windows app is still open game. Between Win32::GUI and wxPerl, I prefer the latter to be more platform agnostic. The wxPerl people unfortunately still need to take care of themselves. It will be wonderful if we can have ActiveState not only support it at the repo level, but ENHANCE and include it as part of the PDK offerings. 2. Excite people back into the Perl community through the fame of the technologies that are supported by the language. Looking at indexing engines, we have Swish-E (with almost exclusive Perl libraries for extension), and Kinosearch (with a responsive maintainer helping the guys on the mailing list). POGL was recently revised to version 0.55 with PPM support. Think of the ASF building projects around it. Make ActiveState the reference point of all these exciting activities. Just my thoughts. Jan Dubois wrote: > > Please note that ActiveState is not trying to create competing > implementations to the open source community. Even if we wanted to, we > simply would not have the resources to do that. It takes a full > community to eventually arrive at a working, maintainable, > production-quality implementation. > > I understand that many people are frustrated by the amount of time > that has elapsed since the idea of Perl 6 was first discussed. But > some things simply cannot be rushed beyond a certain speed; otherwise > you have to redo them as soon as you finish your first draft… > > ActiveState can help with packaging of pre-built binaries, providing > installers and additional tools. But I feel that it is still too early > to do this for Perl 6. I think we should spend any additional time we > find on improving our Perl 5 support instead. > > But I’m also interested in hearing what other people out there thing > that ActiveState should be doing. > _______________________________________________ ActivePerl mailing list ActivePerl@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
