i just received a notice from activestate saying they are cancelling all dealings with perlex! what is up with the short notice! no more bug fixes or anything....PERFECT.
Email Received:
This letter provides notification of the end of engineering support for ActiveState PerlEx, effective immediately. ActiveState is committed to meeting our customers' needs in ways that prove most beneficial both to them and to the dynamic language community as a whole. With this in mind, we have decided to better allocate our Perl development and support resources. If you have any questions, please email me at ShantelS@ActiveState.com, or call me directly at 604.484.6454. Thank you for evaluating PerlEx. We look forward to working with you to support your future development needs. Sincerely, Shantel Shave _____________ Shantel Shave, Director of Marketing, ActiveState Email: ShantelS@ActiveState.com Tel: 604.484.6454 www.ActiveState.com


This isn't a technical question but it does pertain to perl. I was wandering if anyone else was blind sided by this or if i just missed the warning memo?

Any chances on them releasing or liscensing the source code out to the perl community in order to assist those who still loyally use it?

Curious to hear your comments, thanks - Bob

Replies are listed 'Best First'.
Re: Perlex END OF LIFE
by Molt (Chaplain) on Oct 04, 2004 at 16:33 UTC
      yes they will continue to support helping you install a dead product...but what about helping the people that still use and have used that product for a long time. ActiveState is completely abandoning them by their following statement

      Although there will be no further maintenance updates or bug fixes for PerlEx, we will continue to offer existing PerlEx customers standard support (installation and configuration) through March 31, 2005. There are no plans to de-activate the PerlEx discussion list or remove product documentation on ASPN.

      Who wants to know how to install a product that is dead?? Why would they just pull the rug out like that? Does anyone have any insight on this situation? I am utterly befuddled!

        Two words: BEAN COUNTERS, obviously it is not a profitable item. Getting stuff to work with M$ products with their somewhat unstable and inadequately documeneted APIs may also have been an issue.