>> The fact that these modules are not supported by Perl Inc. means that
>> you may feel a bit....hanging over the edge. It is not a secure place.
>> to be if you are a CIO. If you then look at Java which has a more
>> centralized/controlled library, you can at least be sure that the core
>> is supported by Sun (although at a high cost).
>
> My guess is that if you [not you Selena, but the "general you"] get hooked
> up with the right Perl people (possibly through ActiveState if you don't
> know where to go otherwise) you can get more flexible[1] and cheaper Perl
> support.
Good ways around the "but who can we sue?" have been beaten into
horseburgers here before: look at the relase on existing contracts,
who'se support to you really believe in and get good, wholesome answers
from on a regular basis? Oracle, MS and Sun don't usually come up on
those lists, but people do still use them. Ask when the last time was that
Sun fixed a Java Library bug just for you. q.e.d., having a support contract
may not get you very far.
Main worry I encounter w/ "free" support is that someone facing a
deadline and 50 ticked off users won't get an answer to a stupid
question that they just don't have time (brains?) to find themselves.
It's nice to know that someone out there has to answer you.
Answer is AS, "Perl Care" I think used to offer support (see old TPJ),
maybe Cygnus? maybe LinuxCare?
