How does mentioning Catalyst help somebody who is struggling with their first CGI program, and has problems with when variables interpolate and when not? Catalyst may or may not be a fantastic framework, but it is at least a few steps away for somebody just starting to learn Perl.
| [reply] |
How does mentioning Catalyst help somebody who is struggling with their first CGI program
FWIW, when I posted this "SEE ALSO" section, it was only apparent the OP did not know CGI, not apparent the OP was just starting to learn perl
Mentioning Catalyst, including offering a walkthrough, demonstrates how Catalyst makes life easier
| [reply] |
So you think that creating at least 10 files, and heaving the concept of Model / View / Controller is helpful for somebody who is just starting with their first program to display a web page, without explaining what that separation is? The screencast is named "introduction", but it doesn't explain the conceptional splits that Catalyst makes, nor does it mention how dispatching goes from the URL to a subroutine.
I understand that some people think that Catalyst (or any other framework) is great and that it greatly reduces their time to produce a running application, but when starting out with a first, small application, the learning curve of a generic framework is far too high to be useful in connection with the concepts that are necessary to understand. You cannot appreciate the magic "routes" dispatchers or how the class hierarchy gets utilized by the framework until you have a larger application to work with. Starting out with a framework that has all these concepts as necessary prerequisites makes things harder, not easier, and I argue that "easier" is "better" in the case of somebody just starting out.
| [reply] |