in reply to CGI (Perl) vs JSP

I've used both Perl (HTML::Embperl) and Java (JSPs and Servlets) for some larg-ish e-commerce sites (vwrsp.com - Perl, and merckeurolabs.de - Java).

The first site was 2 developers for 4 months. The second was 7 developers for 6 months (with 30% of the features of the first, though it did have internationalization requirements that the first did not). For development speed and performance, (mod) Perl won. For code readability and management acceptance, Java won.

Of course the experience (pain) of using both HTML::Embperl and JSPs/Servlets was what lead me to start Pas, which has (IMO) most of the best aspects of both approaches.

Replies are listed 'Best First'.
Re: Re: CGI (Perl) vs JSP
by perrin (Chancellor) on Mar 25, 2002 at 01:18 UTC
    Rather than write your own templating system, I think it would serve you better to look at the other options like HTML::Template and Template Toolkit. If you prefer in-line perl code, Mason is a good option. Nearly all of the perl templating systems compile the template to normal perl code, so there's nothing really unique that I can see about Pas.

    There are also nice systems built on top of some of these, like OpenInteract and Apache::PageKit.

[reply]

In Section Meditations