1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.15 $ -->
<chapter xml:id="faq.languages" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>PHP and other languages</title>
<titleabbrev>PHP and other languages</titleabbrev>
<para>
PHP is the best language for web programing,
but what about other languages?
</para>
<qandaset>
<qandaentry xml:id="faq.languages.asp">
<question>
<para>PHP vs. ASP?</para>
</question>
<answer>
<para>
ASP is not really a language in itself, it's an acronym for Active
Server Pages, the actual language used to program ASP with is Visual
Basic Script or JScript. The biggest drawback of ASP is that
it's a proprietary system that is natively used only on Microsoft
Internet Information Server (IIS). This limits it's availability to
Win32 based servers. There are a couple of projects in the works
that allows ASP to run in other environments and webservers:
<link xlink:href="&url.instantasp;">InstantASP</link>
from <link xlink:href="&url.halcyon;">Halcyon</link> (commercial),
Chili!Soft ASP from
<link xlink:href="&url.chilisoft;">Chili!Soft</link> (commercial).
ASP is said to be a slower and more cumbersome language than PHP, less
stable as well. Some of the pros of ASP is that since it primarily
uses VBScript it's relatively easy to pick up the language if you're
already know how to program in Visual Basic. ASP support is also
enabled by default in the IIS server making it easy to get up and
running. The components built in ASP are really limited, so if you
need to use "advanced" features like interacting with FTP servers,
you need to buy additional components.
</para>
</answer>
</qandaentry>
<qandaentry xml:id="faq.languages.aspconverter">
<question>
<para>Is there an ASP to PHP converter?</para>
</question>
<answer>
<para>
Yes, the server-side <link xlink:href="&url.asp2php;">asp2php</link>
is the one most often referred to as well as <link
xlink:href="&url.asptranslator;">this client-side</link> option.
</para>
</answer>
</qandaentry>
<qandaentry xml:id="faq.languages.coldfusion">
<question>
<para>PHP vs. Cold Fusion?</para>
</question>
<answer>
<para>
PHP is commonly said to be faster and more efficient for complex
programming tasks and trying out new ideas. PHP is generally referred
to as more stable and less resource intensive as well. Cold Fusion
has better error handling, database abstraction and date parsing
although database abstraction is addressed in PHP 4. Another
thing that is listed as one of Cold Fusion's strengths is its excellent
search engine, but it has been mentioned that a search engine is not
something that should be included in a web scripting language. PHP
runs on almost every platform there is; Cold Fusion is only available
on Win32, Solaris, Linux and HP/UX. Cold Fusion has a good IDE
and is generally easier to get started with, whereas PHP initially
requires more programming knowledge. Cold Fusion is designed with
non-programmers in mind, while PHP is focused on programmers.
</para>
<para>
A great summary by Michael J Sheldon on this topic has
been posted to the PHP mailing list. A copy can be found
at <link xlink:href="&url.coldfusion.summary;">&url.coldfusion.summary;</link>.
</para>
</answer>
</qandaentry>
<qandaentry xml:id="faq.languages.perl">
<question>
<para>PHP vs. Perl?</para>
</question>
<answer>
<para>
The biggest advantage of PHP over Perl is that PHP was designed for
scripting for the web where Perl was designed to do a lot more and can
because of this get very complicated. The flexibility / complexity
of Perl makes it easier to write code that another author / coder
has a hard time reading. PHP has a less confusing and stricter format
without losing flexibility. PHP is easier to integrate into existing
HTML than Perl. PHP has pretty much all the 'good' functionality of
Perl: constructs, syntax and so on, without making it as complicated
as Perl can be. Perl is a very tried and true language, it's been
around since the late eighties, but PHP is maturing very quickly.
</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"../../manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->
|
