Kurt said:
> Should we be _making_ Perl anybody's first choice language for any
> particular application? How about encouraging wise decision-making in
> choosing software tools? There's no ANSI-like standard for Perl, and
> for some organizations, that's a legitimate reason not to bank on Perl.
> I'm more interested in the managers who illogically conclude that's a
> legitimate reason not to bank on Perl, and in the managers who don't
> realize that there's a lot of useful Perl going on behind their backs.
Now this is an interesting point. Several programming languages have
standards bodies operating under technology industry associations.
Microsoft has lately done this with some of their products (not just
languages) and has promised to do more of this. Sun has retained
control over Java standards.
How is this difference from the open source sub-community that sets
standards and direction for Perl? Presumably there is more formality
of process imposed by these standards bodies - but I'm not so sure about
that, there's quite a lot of process discipline that has developed
around the Perl6 effort in particular.
What organizations consider external standards bodies a key requirement
for using a technology? What are some legitimate reasons why this might
be seen as essential?
-Jason
