This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: RE: Bugzilla rewrite in PHP From: Dan Moore <moore@xor.com> Date: Tue, 21 Nov 2000 15:35:14 -0700 (MST) On Tue, 21 Nov 2000, Matt Masson wrote: ... > I wasn't planning on starting a rewrite myself.. just wanted to see what > others thought about it in general. The main thing I was wondering was what > the best fit would be language/architecture wise. I'm convinced that the CGI > has to go.. so if not PHP, then what would work best? I feel that eventually > the code base will need a total rewrite, but I'm not saying that now is the > time for it. > > HTML::Mason looks interesting. Personally, I'll work in whatever language > fits best for the situation.. if HTML::Mason allows for something that > resembles the speed of PHP but keeps the familiarity of Perl, then I'd > support it whole heartedly. I've only looked briefly at HTML::Mason, but it seemed that it didn't divorce the html entirely from the logic (you can embed perl code, no?). I really like the Template module, (http://www.cpan.org/modules/by-module/Template/Template-Toolkit-1.07.readme). Of course, that raises other issues (like, when someone customizes a template, then wants to upgrade to a different version [with perhaps different fields], how do we allow that?). === Subject: RE: Bugzilla rewrite in PHP From: "Matt Masson" <matthew@zeroknowledge.com> Date: Tue, 21 Nov 2000 16:34:43 -0500 I've been using PHP for the past couple of months, and I must admit that I really like it. It's not a perfect language and has its shortcomings, but I have yet to work with a language that doesn't. It has many advantages over Perl, though. While it doesn't have a built in DBI like database interface (yet), it's not all that difficult to create your own (I've seen many implementations of it in code libraries already). Although it was casually mentioned, its multi-platform nature is one of its greatest strengths. Whether running as a server module or as a CGI application, PHP code can be ported to any supported platform with no changes at all. It supports Apache and IIS (which covers 90% of web servers), and we'll no doubt see a whole slew of ports in upcoming months. If anything, I think that the Sourceforge project is a great example of why PHP can easily be used for large scale projects. Do you think you'd have an easier time managing the code base if it was a collection of Perl CGI scripts? The performance of the sourceforge system (through HTTP or SSL) is pretty impressive.. I highly doubt anything CGI based could come close. I agree that PHP might not be the best way to go.. I'm interested in investigating alternatives, though. ===