Re^8: What is the Perl Web Framework du jour?

It certainly seems from reading the above that Jesse was, in 2001 at least, advocating putting the entire codebase, or nearly so, for an application in a single file.

He's arguing for putting all of the controller code for one application into a single file. I can't see anything to disagree with about that. He doesn't say "jam all of your applications for a whole site into one file" nor does he say "put all the database code and templates into one file." I understand what you're objecting to, but it isn't a view supported by Jesse or any of the current CGI::Application developers.

Comment on Re^8: What is the Perl Web Framework du jour?

Replies are listed 'Best First'.
Re^9: What is the Perl Web Framework du jour? by mr_mischief (Monsignor) on Mar 26, 2009 at 21:31 UTC
I think I see where we were talking past one another. I consider most of the sites I design to be one big, integrated application with several related modules. If you have a bunch of separate smaller applications on the same site, I can get behind that idea. You might consider what I'm talking about as a large application as several independent but related applications that happen to use the same classes, templates, user records, application data, and session information across them.	[reply]

Replies are listed 'Best First'.

Re^9: What is the Perl Web Framework du jour?
by mr_mischief (Monsignor) on Mar 26, 2009 at 21:31 UTC

I think I see where we were talking past one another. I consider most of the sites I design to be one big, integrated application with several related modules. If you have a bunch of separate smaller applications on the same site, I can get behind that idea. You might consider what I'm talking about as a large application as several independent but related applications that happen to use the same classes, templates, user records, application data, and session information across them.

[reply]