« Thoughts on a Catalyst Roadmap | Main | Moved Draft of Perl Recruiter FAQ to Github »

10/11/2012

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a0128764b0ec7970c017ee4194775970d

Listed below are links to weblogs that reference Thoughts on a Catalyst Roadmap:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Mamod Mehyar

Thank you, this was a great read, I like Catalyst but at the same time I have the same thoughts you brought up.

For being heavy this totally depends on the project you are working on, if it's a big project then size of Catalyst doesn't matter but when you deal with small sized projects or a light web application then I think catalyst is not for the task, but again I really like the way Catalyst work and how it separate things for me, and since my work mostly deal with small applications I had to roll my own web framework module which resemble Catalyst to some point but as simple as Dancer.

I wish I had the choice of keep using Catalyst on all my projects since it's well engineered, mature and has a great community.

I'm with Catalyst being a thin layer or at least a thin layer port of it will be a great idea

Alan

Good thoughts. I'd add two more considerations:

1) What level of developer expertise is expected? Is Catalyst for beginning developers or for experts?

2) What kinds of websites/applications is Catalyst for?

In other words, who is the customer and what problem is he trying to solve?

The comments to this entry are closed.