Timwi wrote:
Hi,
the past few days I've been experimenting a bit with Apache, mod_perl,
MySQL and creating an entire own website. I've never done that before,
and I think I've learnt a lot from this.
Now, for some reason, against all of your advice, I have started to
program a Wiki, and by now it's already become a suitable basis for a
Phase-IV Wikipedia software, including a database schema.
It really doesn't seem to be very difficult to re-program the current
software in Perl, this time taking all the problems into account and
designing everything right from the start (incl. single-login,
multi-language watchlists, a better translation system and skin system
(separated from the code), etc.) I've also made a lot of
considerations and decisions with respect to database design and
performance.
Should I continue with this?
I wouldn't advise it. While making a simple wiki software is simple
enough, once it startrs getting abigger and more complicated there is a
lot more to be done. Plus, I think there was a reason behing programming
in php vs Perl, im not sure.. but a re-write in a different language
sounds a bit risky. Then add to that that you designed a new db schema
and that all data will have to be converted from one to the other and
you got yourself another issue. I think this is one of those times
where "If it's not broken, don't fix it" I currently see no problems
with the wiki software as it is. I mean sure we have a couple of issues
here and there, but I dont think that means we need to re-write all the
code. What I think would be more important is a clean-up of the code.
And hopefully making the current code use a templating system. After
that we could slowly move towards universal logins through a simple
system I proposed earlier which would allow for a simple transition.
After that is done, we could start working on unifying watch lists. etc.
But at the moment I think its more important to keep the current
software running without interruptions and optimizing it so it can deal
with the high loads it has to handle.
Iwould however be very interested in seeing your DB schema and some info
about your ideas for then ew software before completely shooting down
the idea. just please don't post perl source full of perlisms like $/,
$_, $? @var, %var. etc that crap is obfuscated and hurts my eyes.. i
absolutely hate it. Hell if it was up to me, everything would be
written in something in between c++ and php and there would be no such
thing as arrays, only vectors.
Lightning