On Fri, Jul 25, 2003 at 10:50:53PM +0200, Magnus Manske wrote:
Well, IMHO you *should* continue if you accept that it
might be "just
for the fun of it" and never actually used. I learned PHP/MySQL while
writing code for Nupedia, which died soon after my code went online (no
cause and effect here;-)
*If* we decide to work on a Phase IV (one of my favourite movies BTW), I
think we should go for C++. Two main reasons:
- Probably the fastest way to work with arrays of char (=plain text),
which is most of the internal working of a wiki software
- Real OOP, in contrast to the PHP-class jokes. If we design a database
class in C++, for example, the actual queries could be entirely capsuled
from the rest of the program. That would make switching database
versions or even databases (MySQL/Postgres/???) much easier.
Capsuled classes will also make it easy to write stand-alone-programs
for offline reading, as I tried. A proof-of-principle-viewer is
available in C++.
The main reason *not* to use C++ is that I don't know how to turn such a
program into an apache module. Help on that would be appreciated.
Have you lost all self-preservation instinct already ?
C/C++ is absolutely the most insecure option that exists.
And if you want to use arrays of chars, you may as well turn off
the root password - at this point it doesn't really make any different.
If speed was crucial we can use Ocaml, Common Lisp, compiled Java,
or one of a few other compiled and GC-ed languages with clear separation
of data and code.
Not to mention that using arrays of chars with hand-written parsers for them
is almost always slower than naive Perl regular expressions, unless
parsed language is really trivial, and it's not ever comparable in speed