Hi,
You must think about of what you wanna do... you can't say X is better than Y, because that's not true...
You can't even say that for develope webpages is better one than another, you must do a strict analysis, really!
If we talk about webpages, a website you must think about the scalability, not only how much traffic, how many request can give solution X or Y, you must think about: what new functionality I must provide tommorow... how many updates will be done to the webpage... who will make they... and a large etc. Because answering this question you can know if what you need is a webpage that gets admin. by admin (content also) or you need a CMS, or need a independent solution (like Bricolage) etc...
You must be able to distinguish between a web-site and a web-app. If you need a web-app then you can think about what kind of webapp would it be... do it conforms to the MVC model? If yes, then you can think about CGI::Application, Maypole, Catalyst, etc...
I use some technologies. For website I use often Mason, because I have a lot of code written that I can reuse. I also have some webapp written with Maypole, it's very easy (this remember me that I should update some servers to the latest version of Maypole, which supposed to fix speed issues). I also read the Catalyst documentation, expecting to begin in a few weeks a refactoring of a big webapp.
Resuming, you should think about what you really want to do, and then choose the easiest solution that also let you scale to the 1 year forward expectations/requirements.
K.I.S.S.
Regards,
In reply to Re: Maypole or PageKit?
by fmerges
in thread Maypole or PageKit?
by ait
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |