C
Charlton Wilbur
JC> You have a point. On the other hand, other commercial OSs
JC> (such as, I believe, Mac OS X and Solaris 9) come with several
JC> well established free software packages, including several GNU
JC> utilities and Perl. Companies like Sun and Apple also don't
JC> have control over Perl, so why do they include it?
Microsoft already *has* a language aimed at the same problem space as
Perl: Visual Basic. If they provided Perl, they'd be weakening Visual
Basic's position on the Windows platform. Beyond that, by providing
Windows-specific tools, they lock people into the Windows platform: if
you want to do scripting on Windows, you need to learn Visual Basic;
and that Visual Basic knowledge is not transferable to Linux or
Solaris or OS X at all.
By contrast, there's little benefit to Apple to create an Apple-only
general-purpose scripting language[1]: the amount of effort necessary
to be specifically contrarian in this could give much greater returns
elsewhere. The same can be said for Sun: the benefits of including
Perl are *much* greater than the benefits of not including it,
especially since many people would likely just install Perl anyway.
Charlton
[1] AppleScript doesn't really count - it's an extremely high-level
glue language that plays well with the Cocoa framework.
JC> (such as, I believe, Mac OS X and Solaris 9) come with several
JC> well established free software packages, including several GNU
JC> utilities and Perl. Companies like Sun and Apple also don't
JC> have control over Perl, so why do they include it?
Microsoft already *has* a language aimed at the same problem space as
Perl: Visual Basic. If they provided Perl, they'd be weakening Visual
Basic's position on the Windows platform. Beyond that, by providing
Windows-specific tools, they lock people into the Windows platform: if
you want to do scripting on Windows, you need to learn Visual Basic;
and that Visual Basic knowledge is not transferable to Linux or
Solaris or OS X at all.
By contrast, there's little benefit to Apple to create an Apple-only
general-purpose scripting language[1]: the amount of effort necessary
to be specifically contrarian in this could give much greater returns
elsewhere. The same can be said for Sun: the benefits of including
Perl are *much* greater than the benefits of not including it,
especially since many people would likely just install Perl anyway.
Charlton
[1] AppleScript doesn't really count - it's an extremely high-level
glue language that plays well with the Cocoa framework.