in reply to Re: Perl advocacy, CGI/ModPerl vs ASP/JSP
in thread Perl advocacy, CGI/ModPerl vs ASP/JSP

  • Slashdot gets a lot of hits and runs perl. <...> In the end it all comes down to good design and network architectures.

    • Doesn't Slashdot have a big fat load balancing system in place? The speed issue was dealt with by throwing more hardware at the problem. So, like you said, it comes down to design and achitecture. I suppose somebody could code a website using Q-BASIC on several heavy duty machines behind a load balancing system, but that's probably not good design.

    To me, I find Perl very fast and easy to develop with. Not only is CPAN sweet, but PerlDoc rocks as well. I use references constantly when I code, and PerlDoc is always there when I need a hint.

    • Comment on Re: Re: Perl advocacy, CGI/ModPerl vs ASP/JSP

    Replies are listed 'Best First'.
    Re: Re: Re: Perl advocacy, CGI/ModPerl vs ASP/JSP
    by perrin (Chancellor) on Jun 17, 2002 at 19:30 UTC
      They describe the machines that power the site here. I wouldn't call 10 Intel boxes a big fat system. They probably cost less than one Sun box.
    		[reply]
        More importantly, if it is a problem that can be solved by throwing more computers at, then you have a linear growth scalability. If you have a bad implentation, like bad algorithims, you could end up with an exponential growth, which cannot be fixed by throwing more computers at it. Perl can obviously support good programming and linearly scalable systems.
    		[reply]
    Re: Re: Re: Perl advocacy, CGI/ModPerl vs ASP/JSP
    by Matts (Deacon) on Jun 17, 2002 at 16:32 UTC
      Slashdot actually used to be fast, and back then it ran out of Malda's appartment. (I have a userid in the 2000's). It requires a big fat pipe because it uses it. It requires load balancing because it gets enough traffic to need a big fat pipe.
    		[reply]

    In Section Meditations